UiPath Orchestrator Guide

About Robots

A Robot is an execution host that runs processes built in UiPath Studio.

The Robots page enables you to add robots, edit them, view their status and license state, change runtime settings and the environment(s) they are assigned to. Additionally, you can display the logs generated by a single Robot.

Note:

When a Robot is busy (executing a process), you cannot edit the following information:

  • Username
  • Machine
  • Type

Robots can execute processes under custom settings. You can configure logging and resolution in the Runtime tab while provisioning or editing a robot.

In this page, Attended and Development Robots also display their licensing status, in the Username column, as displayed in the screenshot below - a Robot is marked with a green icon if it has acquired a license, or orange when it is not using its license. If the machine the Robot is installed on is offline or the UiPath Robot service is stopped, nothing is displayed.

A grouping of Robots is called an environment and enables you to execute the same package on multiple Robots at the same time.

Important!

If you have multiple Robots on the same machine, it is recommended that you group them in the same environment and Orchestrator tenant. Otherwise, some errors might occur when deploying different versions of the same process.

Types of Robots

  • Attended - works on the same workstation as a human user and is usually triggered by the user through their actions (user events). You cannot start processes from Orchestrator on this type of Robots, and they cannot run under a locked screen. They can be started only from the Robot tray.
  • Unattended - runs unattended in virtual environments and can automate any number of processes. On top of the Attended Robot capabilities, this Robot is responsible for remote execution, monitoring, scheduling and providing support for work queues.
  • NonProduction - retains all the features of the Unattended Robot, but it should be used only for development and testing purposes.
  • Development - has the features of an Unattended Robot, but it should be used only to connect your Studio to Orchestrator, for development purposes.

All types of Robots can run in debug in Studio.

For more information, see the UiPath Robot Documentation Portal.

About High-Density Robots

Regardless of the Windows version a machine is running on, if you have multiple users on it, you can register a Robot on each of the users.This feature is called High-Density Robots and ensures a full utilization of each machine at your disposal at its maximum potential. It can be applied to all types of Robots (Attended, Unattended and NonProduction).

The High-Density environment has the following advantages:

  • On a machine with a Windows Server (2008 R2 or 2012 R2 or 2016) operating system:
    • you can run the same process with all Robots in the same time;
    • you can run different processes with all Robots in the same time.

To set up High-Density Robots on a Windows Server machine, please see the Setting Up Windows Server for High-Density Robots chapter.

Note:

On the same machine, you have to connect all users as Robots to Orchestrator, all with the same Machine Name and Key.

If you register a new Robot to Orchestrator on a machine while the UiPath Robot service is running, you have to restart the service.

If the username and/or password filled in when deploying the Robot to Orchestrator do not correspond to the Windows credentials for the specified user, the first job you run is faulted and a "Logon failure" message is displayed in the Job Details window.


About Robots