UiPath Orchestrator

The UiPath Orchestrator Guide

How the Connection Between the Robot and Orchestrator Works



A Robot is uniquely identified through a machine name, a username, and a machine key.
A Floating Robot is uniquely identified through an Active Directory username and a machine key.

After you registered one or multiple Robots from the same machine to Orchestrator, you are required to add the Machine key and Orchestrator URL in the Orchestrator Settings window, as mentioned in the Connecting Robots to Orchestrator page.

Once the information is complete and you click Connect, Orchestrator checks its database and tries to find a match with the machine name and key added in the Orchestrator Settings window.

If a match is found, Orchestrator sends back a list of all the Robots with the specified machine name and key. From here, the Robot is registered to Orchestrator and appears online in the Robots page. The Robot starts reporting its status every 30 seconds.

If you are connecting Studio to Orchestrator through the Robot, an authentication token, called a bearer token, is also send from Orchestrator. This token is then passed to Studio. The authentication process is refreshed every 30 minutes, according to the default value of the Auth.Bearer.Robot.Expire parameter.

If the connection between Orchestrator and a Robot is lost for any reason, the last known status of the Robot is displayed in the Robots page and a red exclamation mark indicates that the Robot has not sent a status update in the last 2 minutes.

Updated 3 years ago

How the Connection Between the Robot and Orchestrator Works

Suggested Edits are limited on API Reference Pages

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