The Robot is UiPath’s execution agent that enables you to run processes developed in Studio. Robots need to be connected to Orchestrator in order to execute processes or they have to be licensed locally (read more about licensing). The type of Robot you have at your disposal is determined by the license, while the Robot service is determined by the deployment.
The Robot is split into four components, each being dedicated to a particular task in your automations. The Robot components are as follows:
Having the Robot components split as explained above helps developers, support users, and computers easily run, identify, and track what each component is executing. Special behaviors can be configured per component this way, such as setting up different Firewall rules for the Executor and the Service.
The Robot can open interactive Windows sessions, under the Local System account, and has all the rights of a Windows service.
Installing the Robot using
UiPathStudio.msi deploys the SCM-managed Robot Service by default. It can also be installed from the Command Prompt, as explained on this page.
Robots can also be installed in User Mode. For your Robot, this means that it has the exact same rights as the user under which it has been installed. Installing the Robot from
UiPathStudioSetup.exe deploys the User Mode Robot Service by default. It can also be installed from
UiPathStudio.msi, as explained here, or the Command Prompt, as described on this page.
Both the SCM-managed and User Mode Robot service can be configured as HD Robots.
Please note that packages downloaded by the SCM-managed Robot Service cannot be run by Robots in user mode. This is because the SCM-managed Robot Service downloads packages in the Local System (not the local user), and the Robot in user mode does not have permissions for that folder. If this happens, it is recommended to delete all packages downloaded by the SCM-managed Robot Service, which are located in the
Regardless of the mode in which you installed the Robot, it can still be connected to Orchestrator. Please note that closing the Robot Agent (tray) does not close the UiPath Robot service.
Updated about a month ago
|The User Interface|
|About Automation Projects on the Robot|
|About High-Density Robots|