- Release Notes
- Getting Started
- UiPath Assistant
- Installation and Upgrade
- Robot Types
- Robot Components
- Robot Service
- Robot Executor
- Command Line Interface
- 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
- Common Connection Errors
- 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
Robot Executor
The robot executor (UiPath.Executor.exe) is the robot component directly responsible for executing a process. When a job is started, the robot service launches a robot executor instance.
The Executor is always aware of DPI settings per-monitor. As a result, workflows can be executed at any DPI, regardless of the configuration on the machine they were created on. For apps that are DPI-unaware, or intentionally marked as unaware, you can choose to disable DPI.
Based on the automation project, the robot service launches the type of executor intended to run the automation.
There is a type of executor for each of the automation project type available:
|
Project Type |
Architecture |
Supported platforms |
Framework |
|---|---|---|---|
|
Windows - Legacy |
32-bit |
Windows (32-bit and 64-bit) |
.NET Framework 4.6.1 |
|
Windows |
64-bit |
Windows (64-bit) |
.NET 6 with Windows support |
|
Cross-platform |
64-bit |
Windows, Linux, and macOS (64-bit) |
.NET 6 with cross-platform support |
Always having an additional executor ready to run an automation improves process execution start time.
By default, the following pre-loaded executors are automatically launched when the robot starts:
-
On Windows : Windows and Legacy
-
On Mac : Cross-platform (Portable)
You can overwrite the default behavior by adding the UIPATH_PRE_LOADED_EXECUTOR user environment variable to the robot machine with the value None. This way, the pre-loaded executor only starts when the first process is run.
To completely disable the pre-loaded executor feature, add the UIPATH_DISABLE_PRE_LOADED_EXECUTOR environment variable to the robot machine with the value set to "True".
The pre-loaded executor feature is only available for attended execution processes started from UiPath Assistant, RobotJS, Studio, or the command line interface. An unattended job started from Orchestrator launches a single executor when the job starts.
