Introduction to UiPath Robot

UiPath Robot execution agent: components, licensing models, and connection to Orchestrator for running Studio-built processes.

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 several components, each being dedicated to a particular task in your automation. The Robot components are as follows:

• Service
  • Service Mode
  • User Mode
• Executor
• Command Line Interface
• UiPath Assistant

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.

Service Mode and User Mode robots

The Robot can open interactive Windows sessions, under the Local System account, and has all the rights of a Windows service. Learn more about Windows sessions.

• Installing the Robot using UiPathStudio.msi deploys the Service Mode Robot by default. You can also install it from the Command Prompt.
• User Mode Robot has the same rights as the user under which it was installed.
• Both Service Mode and User Mode Robots can be configured as HD Robots.

Note:

Packages downloaded by the Service Mode Robot cannot be run by User Mode Robots. The Service Mode Robot downloads packages under the Local System account, which the User Mode Robot cannot access. If this happens, delete the packages in %userprofile%\.nuget\packages and re-download.

Regardless of the mode in which you installed the Robot, it can still be connected to Orchestrator.