Robots
Robot list, monitoring, connectivity status, and usage metrics from synced RPA providers
Robots (also called agents or machines) are the entities that physically execute your processes. RPA Watch syncs robot information from your connected RPA tools and tracks their activity.
Robot List
Navigate to Robots in the sidebar to see all robots in the current account. The list shows:
- Name — Robot display name (from the RPA tool)
- Type — Robot type (e.g., Attended, Unattended, Cloud)
- RPA Tool — Which tool this robot belongs to (Robomotion, UiPath)
- Last synced — When the robot data was last updated
Robot Properties
| Property | Description | Source |
|---|---|---|
| Display name | Synced from RPA tool | |
| ID in the source RPA system | Synced | |
| Robot type (varies by tool) | Synced | |
| Physical machine name (UiPath) | Synced | |
| Workspace identifier (Robomotion) | Synced | |
| Robot description (UiPath) | Synced | |
Robot Types by Tool
Robomotion
Robomotion robots have types defined by the Robomotion platform (Cloud, Desktop, etc.).
UiPath
UiPath robots come in several types:
| Type | Description |
|---|---|
| Works alongside a human user | |
| Runs autonomously without user interaction | |
| Development robot | |
| Citizen developer robot |
Robot Usage Metrics
The Dashboard includes a robot usage section that shows:
- Number of jobs per robot (over a time period)
- Success/failure rate per robot
- Most active robots
- Last activity date
This helps you identify:
- Overloaded robots — Too many jobs, potential bottleneck
- Underutilized robots — Robots with very few jobs
- Unreliable robots — High failure rate may indicate infrastructure issues
Syncing Robots
Robots are synced automatically every 15 minutes as part of the [automatic sync](/docs/automatic-sync) process. They can also be synced manually by clicking the Sync button on the Flows page.
Orphan Detection
If a robot is removed from your RPA tool (decommissioned, deleted), it is soft-deleted in RPA Watch:
- It no longer appears in the robot list
- Historical jobs that reference the robot are preserved
- If the robot reappears in a future sync, it is restored
Robot Monitoring
You can enable monitoring on individual robots to track their connectivity status in real time. When monitoring is enabled, RPA Watch checks the robot's live status via the RPA provider's API.
Enabling Monitoring
1. Navigate to Robots in the sidebar
2. Find the robot you want to monitor
3. Click the monitoring toggle in the Monitoring column (Account Admin or Tenant Admin required)
When you enable monitoring, RPA Watch immediately checks the robot's current status.
Status Indicators
| Status | Indicator | Description |
|---|---|---|
| Green dot | Robot is online and available (Available or Busy session) | |
| Red dot | No active session found or session is in a non-available state | |
| Gray dot | Status has not been checked yet |
How Status Checking Works
- When monitoring is enabled, RPA Watch queries the RPA tool's Sessions API (currently supported for UiPath)
- The robot is matched to a session by its external robot ID, or by machine name as a fallback
- A session with state "Available" or "Busy" means the robot is Connected
- If no matching session is found, the robot is marked as Disconnected
Robot Offline Alerts
If a monitored robot goes offline and [alerts are enabled](/docs/alerts) for the account, RPA Watch can generate a robot_offline alert. This notifies the process owner and members via email so you can take action quickly.
Robots in Jobs
Each job can reference the robot that executed it. This is set automatically for synced jobs and can be specified via the robot_id field in the Ingest API.