robot
2023.4
false
- Release Notes
- Getting Started
- Installation and Upgrade
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Robot JavaScript SDK
- Specific Scenarios
- Restarting Robot Components
- Windows Sessions
- Login Using Thales Luna Credential System
- Login Using NShield Key Storage Provider
- Redirecting Robots Through a Proxy Server
- Executing Tasks in a Minimized RDP Window
- Using Mapped Network Drives
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike integration
- Robot Citrix Apps Virtualization
- Troubleshooting
- Unresponsive Robot Over RDP
- Duplicate Execution Logs
- Frequently Encountered Robot Errors
- Increased Process Execution Duration
- Enforced Package Signature Verification
- Message Too Large to Process
- Errors When Running as Administrator
- NuGet Packages Not Accessible After Migration
- User Access Control Prompt and UI Automation Activities
- .NET required during installation
- Assembly Cannot Be Loaded From Network Or Azure File Share
- Activities cannot find .NET Runtime
- CrowdStrike integration troubleshooting
Message Too Large to Process

Robot User Guide
Last updated Feb 5, 2025
Message Too Large to Process
Processes using large amount of data (e.g. Excel files with more than ~2500 rows) can fail with the following error:
Message: Could not retrieve the result of the job execution. This might be because a message was too large to process.
Exception Type: System.Exception
Message: Could not retrieve the result of the job execution. This might be because a message was too large to process.
Exception Type: System.Exception
The output of the job execution exceeds the maximum configured value of the
maxMessageSizeInMegabytes
parameter in the uipath.config
file.
This parameter has a maximum value of 10 MB.
To resolve this, configure the workflow to save the output in a storage bucket in Orchestrator or in Data Service instead of using an output argument.
Read more below: