- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Setup Samples
- Storing Robot Credentials in CyberArk
- Setting up Attended Robots
- Setting up Unattended Robots
- Storing Unattended Robot Passwords in Azure Key Vault (read-only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read-only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Audit
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Integrations
- Classic Robots
- Troubleshooting
Robot Statuses
Only displayed for attended robots. Displayed in front of the license type in the Type column, as in the screenshot below. The following options are available:
- Green icon - licensed. Hovering over the icon displays the exact time and date the license was acquired.
-
Red icon - unlicensed
If the UiPath Robot service is stopped, nothing is displayed.
The following options are available:
Available - UiPath Robot is not running a process and is free to be used.
Busy - UiPath Robot is running a process. You cannot edit the username, machine and license type of a busy robot.
Unresponsive - UiPath Robot and Orchestrator have not communicated in the last two minutes.
Disconnected - the UiPath Robot service is not running.
On the Robot page, Management menu, the connection status is the last known status of UiPath Robot as communicated through the most recent heartbeat. Hovering over this field displays the date and time of the last heartbeat.
Attended standard robots are displayed as Connected, Unlicensed if you quit the tray. That's because the UiPath Robot service is still up and running. You have to stop the service such that the robot disconnects. For the rest of them disconnecting your UiPath Robot from the tray causes the corresponding robot to appear as disconnected in Orchestrator as well.
