UiPath Robot

The UiPath Robot Guide

High-Density Robots

For a better use of a machines's computing power, Robots can be configured in High-Density mode. This way, regardless of the machine's Windows Server version. If you have multiple users on it, a Robot can be registered under each user so that you can make the most out of the computing power available on that machine.

Any type of Robot (Attended, Unattended or NonProduction) can be configured in a High-Density environment.

The High-Density Robots can be installed in User Mode for attended uses. The Community Version provides the option to deploy the feature by default as the Robot is part of the installer. If you choose to configure this feature using the MSI installer, please follow the steps described here to deploy the High-Density Robots in User Mode.

The High-Density environment has the following advantages:

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



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

If you register a new Robot to Orchestrator on a machine running the UiPath Robot service, you do not have to restart the service. It is recommended to wait at most 30 seconds for the heartbeat to be submitted.

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

It is recommended to connect all the Robots from one machine to the same Orchestrator tenant, and in the same environment.

Updated about a year ago

High-Density Robots

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.