Limits

Limits that apply to UiPath Robot 2026.10 on machines you manage, for job duration, concurrency, and each operating system.

These limits come from the machine or the workload, not from your license. Limits that a license sets, such as the number of runtimes, are on Licensing the Robot.

Job duration

The Robot doesn't limit how long a job runs, for any workload. Agents, functions, and API workflows on your own robots have no job duration limit, and neither do RPA processes and test cases.

Two time limits apply around a job:

• Startup: installing the packages a job needs, and starting the host process for an executor package, must finish within the InstallPackageTimeout set in UiPath.config, 20 minutes by default.
• Forced stop: when you kill a job, the Robot gives the job a grace period to flush its logs: 30 seconds by default, which is 25 seconds plus 5. Set UIPATH_KILL_FROM_SERVICE_FLUSH_TIMEOUT, in seconds, to change the 25. After the grace period, the Robot ends the process of an RPA process or test case. For an agent, function, or API workflow, it fails the job, and ends the host process only if it couldn't deliver the stop.

Concurrency

Workload	Limit
Foreground RPA process	One at a time for each Windows user, and one in the console session, however many runtimes the machine has. On Windows Server, several users can each run one in their own RDP session.
Background RPA process or test case	The runtimes on the machine object
Agent	The Agent slots on the machine template, for each connected machine
Function or API workflow	The Function slots on the machine template, for each connected machine. Or the machine's Production (Unattended) runtimes, shared with RPA jobs, when Use Production (Unattended) is selected on the machine template.

Logs, messages, and sessions

The Robot enforces these limits by default. You can change each one.

Limit	Default	How to change it
Verbose logs for each Executor process. The Robot logs a warning and drops further Verbose logs.	10000	UIPATH_VERBOSE_LOG_LIMIT, refer to Log levels
Size of a message that Robot components send or receive, such as the data an automation returns	10 MB	MaxMessageSizeInMegabytes in communicationSettings, refer to Configuration files
Wait for a response between Robot components	40 seconds	RequestTimeout in communicationSettings, refer to Configuration files
Creating an interactive session	60 seconds	UIPATH_SESSION_TIMEOUT, refer to Configuration files
Starting a process in a Robot session	180 seconds	UIPATH_PIP_SESSION_TIMEOUT, refer to Configuration files

Operating systems

Operating system	Limit
Windows	ARM architecture is not supported. High-Density Robots require Windows Server.
Linux	Docker image only. Unattended, cross-platform automations only. No automatic updates: deploy the image of the newer version.