UiPath Robot Guide

Introduction

The Robot is UiPath’s execution agent that enables you to run workflows built in Studio.

A Robot is installed as a Windows Service by default. As a result, the Robot can open Windows sessions (interactive or non-interactive), under the Local System account, and has all the rights of a Windows service.

Robots can also be installed in a user mode. For your Robot, this means that it has the exact same rights as the user under which it has been installed.

Regardless of the mode in which you installed the Robot, it can still be connected to Orchestrator. Please note that closing the Robot tray does not close the UiPath Robot service.

Robots need to be connected to Orchestrator in order to execute processes or they have to be licensed locally.

Types of Robots

The license that was chosen dictates a Robot's capabilities, as follows:

  • Attended - operates on the same workstation as a human, to help the user accomplish daily tasks. It is usually triggered by user events. You cannot start a process from Orchestrator on this type of Robots, and they cannot run under a locked screen.
  • Unattended - run 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. Please note that it is the only type of Robot that enables you to execute debugging in Studio.

For more information on licensing, please see the About Licensing.

Connecting a Robot to Orchestrator offers the following benefits:

  • a centralized location from which to deploy automation projects to Robots
  • an easier and centralized point for the management and monitoring of multiple Robots
  • the scheduled execution of automation processes on Robots
  • the management of queues and transactions
  • centralized Robot logging to SQL and/or ElasticSearch

Note:

If a RDP connection is started on the robot machine and this machine loses internet connection, even for few seconds, the Robot throws a “Desktop has been disconnected…” exception.


Introduction