---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# High density robots

# High density robots in Unattended Robot {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Execute multiple automations simultaneously and independently on a single Windows Server machine using high density robots.
Familiarize yourself with high density robots concepts in RPA Hub. For more information, see [High density robots in RPA Hub](https://www.servicenow.com/docs/1VGKwsule~nBzfKBsbVfUw "Execute multiple automations (bot processes) simultaneously and independently on a single Windows Server machine using high density robots.").

## How a high density robot works {#high-density-robots-uat__section_oxr_1nq_ydc}

* The robot can start one automation for each Windows user session at any given time. You can run the same automation on all robots simultaneously. You can also run different automations on all robots at the same time.
* In a scenario, where, a user A is connected to a server via Remote Desktop Protocol (RDP) where a high density robot is connected. If an execution is triggered for the same user A, the manually connected session is disconnected and transferred to the robot. However, the user can reconnect to view the execution after the robot starts its automation.
* When changing the robot type from High Density Robot to standard or vice-versa, you must reconnect the unattended robot to ensure seamless execution of automations. For more information about creating an unattended robot, see [Create an unattended robot in RPA Hub](https://www.servicenow.com/docs/ohH8UbgNkR4cg8cO5vNgyg "Create an unattended robot in RPA Hub to run the unattended bot process.").
{#high-density-robots-uat__ul_vky_xmq_ydc}

## List of steps for configuring high density robots {#high-density-robots-uat__section_i15_wtl_zdc}

Perform the following tasks to configure high density robots:

1. Set up the environment for high density robots on a Windows Server machine by installing a Remote Desktop Session Host. Then, add users who can establish RDP connection to the Windows Server machine. For more information, see [Set up Windows Server machine for high density robots](https://www.servicenow.com/docs/Kwmx~gu5aT2wbiPPdeF0aw "Set up the environment for high density robots on a Windows Server machine by installing a Remote Desktop Session Host. Then, add robot user names who can connect to the machine. It enables them to establish Remote Desktop Protocol (RDP) connection to the Windows Server machine.").
2. Restart the Windows Server machine after the installation is complete.
3. Enable the high density robot option in RPA Hub. For more information, see [Create an unattended robot in RPA Hub](https://www.servicenow.com/docs/ohH8UbgNkR4cg8cO5vNgyg "Create an unattended robot in RPA Hub to run the unattended bot process.").
4. [Install Unattended Robot](https://www.servicenow.com/docs/u7TNde_4fPJ399ezP8DoTQ "You can install the Unattended Robot application in your Windows machine if you have the admin role.").
5. Add user profiles in the Unattended Robot application, so that multiple robots can execute jobs concurrently. For more information, see [Set up Unattended Robot](https://www.servicenow.com/docs/CeL_wmz~elWuU7OhYB2oPw "Set up the Unattended Robot application to establish a connection between a robot and the ServiceNow RPA Hub instance.").
{#high-density-robots-uat__ol_vdr_45l_zdc}

## Troubleshooting {#high-density-robots-uat__section_tv3_jnq_ydc}

* RDP logon errors are recorded in the service logs. Although some logs may lack detailed explanations, utilize the code to search for relevant information in [Disconnect reason code](https://learn.microsoft.com/en-us/windows/win32/termserv/imstscaxevents-ondisconnected) and [Extended disconnect reason code](https://learn.microsoft.com/en-us/windows/win32/termserv/extendeddisconnectreasoncode).
* The underlying application process names used in automations may vary between the server environment and the development environment. To avoid discrepancies, ensure they are correctly specified in the automations based on the target machine.
{#high-density-robots-uat__ul_y3k_knq_ydc}

## Limitations {#high-density-robots-uat__section_ddd_4nq_ydc}

* The Unattended Robot user interface is accessible by only one user at a time.
* The latest version of the Unattended Robot must be installed after upgrading the RPA Hub to the newest version.
* High density robots are not a part of robot pool.
{#high-density-robots-uat__ul_dyv_4nq_ydc}