High density robots in Unattended Robot

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of High Density Robots in Unattended Robot

    High density robots enable the simultaneous and independent execution of multiple automations on a single Windows Server machine. This feature is particularly useful for maximizing automation efficiency within your organization by allowing various automations to run concurrently for different user sessions.

    Show full answer Show less

    Key Features

    • The robot can execute one automation per Windows user session, allowing both the same and different automations to run across multiple robots at the same time.
    • When a user is connected via Remote Desktop Protocol (RDP) and triggers automation for their session, the session is transferred to the high density robot while still allowing the user to reconnect and monitor the execution.
    • Switching between high density and standard robots requires reconnecting the unattended robot for smooth operation.

    Configuration Steps

    To configure high density robots, follow these steps:

    • Set up a Windows Server machine with a Remote Desktop Session Host and add users for RDP access.
    • Restart the server post-installation.
    • Enable the high density robot option in RPA Hub.
    • Install the Unattended Robot and add user profiles in the application to support concurrent job execution.

    Troubleshooting

    RDP logon errors can be traced in service logs, and users are advised to utilize disconnect reason codes for troubleshooting. Ensure that application process names in automations are consistent with those on the target machine to avoid issues.

    Limitations

    • The Unattended Robot interface supports only one user at a time.
    • Ensure that the latest Unattended Robot version is installed after upgrading RPA Hub.
    • High density robots are not included in the robot pool.

    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.

    How a high density robot works

    • 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.

    List of steps for configuring high density robots

    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.
    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.
    4. Install Unattended Robot.
    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.

    Troubleshooting

    • 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 and Extended disconnect reason code.
    • 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.

    Limitations

    • 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.