RPA Orchestrator and Bot Management
An Orchestrator is the command centre for your entire RPA operation. It is a web-based platform where you deploy bots, schedule them, monitor their activity in real time, manage work queues, store credentials securely, and review logs. Without an Orchestrator, each bot runs independently with no central visibility or control.
Think of the Orchestrator as an air traffic control tower. Individual planes (bots) fly their routes, but the control tower sees all of them, manages their schedules, detects problems, and coordinates responses.
UiPath Orchestrator Core Features
Diagram: Orchestrator Feature Map
┌───────────────────────────────────────────────────────────┐ │ UIPATH ORCHESTRATOR │ │ │ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────────┐ │ │ │ ROBOTS │ │PROCESSES │ │ QUEUES │ │ SCHEDULES │ │ │ │Manage │ │Deploy │ │Manage │ │Trigger bots │ │ │ │machines │ │packages │ │work items│ │on time/event │ │ │ └──────────┘ └──────────┘ └──────────┘ └──────────────┘ │ │ │ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────────┐ │ │ │ ASSETS │ │CREDENTIAL│ │ LOGS │ │ ALERTS │ │ │ │Config │ │Vault │ │Execution │ │Notify on │ │ │ │variables │ │Secure │ │history │ │errors │ │ │ │ │ │passwords │ │ │ │ │ │ │ └──────────┘ └──────────┘ └──────────┘ └──────────────┘ │ └───────────────────────────────────────────────────────────┘
Robots (Managed Machines)
In Orchestrator, each bot machine (physical or virtual) is registered as a Robot. The robot can be:
- Unattended Robot: Runs on a server/VM without human interaction. Triggered remotely by Orchestrator schedules or API calls.
- Attended Robot: Runs on a user's workstation. Triggered manually or by a Trigger on the local machine.
- Non-Production Robot: Used for development and testing only. Not billed as a production resource in most licensing models.
Robot Pools
Multiple robots can be grouped into a pool. When a job is triggered, Orchestrator assigns it to any available robot in the pool. This enables parallel processing — 10 bots in a pool can process 10 items simultaneously from the same queue.
Processes and Packages
A Package is the published version of a bot workflow — the deployable archive file (.nupkg) that contains all the .xaml files and dependencies. A Process is the link between a Package and the Robots that will run it. Creating a Process in Orchestrator means "run this package on these robots."
Deployment Flow
Developer builds bot in UiPath Studio
│
▼
Developer publishes bot to Orchestrator
(creates a Package: InvoiceBot_v1.0.0.nupkg)
│
▼
Admin creates a Process in Orchestrator:
Package: InvoiceBot_v1.0.0
Environment: Production
Robots: VM-Prod-01, VM-Prod-02
│
▼
Admin creates a Schedule:
Trigger: Daily at 9 AM
Process: InvoiceBot
Robot Pool: Production Pool
│
▼
At 9 AM, Orchestrator sends the job to available robots
Robots execute the bot and report results back to Orchestrator
Queues (Work Item Management)
Queues store individual units of work that bots process. Each item in a queue is called a Transaction Item. Bots pull items from the queue, process them, and update their status.
Queue Item States
QUEUE: Invoice Processing Queue ────────────────────────────────────────────────────── Item Status Updated By ────────────────────────────────────────────────────── INV-2024-0451 Successful Bot_01 @ 09:05 AM INV-2024-0452 Successful Bot_02 @ 09:06 AM INV-2024-0453 In Progress Bot_01 @ 09:07 AM (currently running) INV-2024-0454 New (waiting for a bot to pick it up) INV-2024-0455 Failed Bot_02 @ 09:06 AM (exception occurred) ──────────────────────────────────────────────────────
Queue Retry Logic
Orchestrator can automatically retry failed queue items. You set the maximum number of retries and the retry delay. A failed item is moved back to the queue for retry on the next available robot.
Assets (Configuration Variables)
Assets store configuration values that bots retrieve at runtime. This avoids hardcoding values inside the bot. When a value changes — such as an email address, a file path, or a threshold — you update the Asset in Orchestrator, not the bot code.
Types of Assets
| Asset Type | Used For | Example |
|---|---|---|
| Text | String values | AP Manager Email = "ap@company.com" |
| Integer | Numeric thresholds | Max Invoice Amount = 50000 |
| Boolean | Feature flags | Send Confirmation Email = True |
| Credential | Username + encrypted password | SAP Credentials = (sapuser / *****) |
Schedules and Triggers
Orchestrator lets you trigger bots using two methods:
- Time Triggers: Run a bot at a fixed time or on a recurring schedule (daily, weekly, monthly, cron expression).
- Queue Triggers: Automatically start a bot when items arrive in a queue. For example, start one additional robot for every 50 items in the queue, up to a maximum of 5 robots.
Cron Expression Example
Run at 6 AM Monday to Friday: 0 0 6 ? * MON-FRI Run every 2 hours: 0 0 0/2 * * ? Run on the 1st of every month: 0 0 8 1 * ?
Monitoring and Alerts
Orchestrator's dashboard shows real-time bot activity. You see which bots are running, which are idle, which jobs succeeded, and which failed. You configure alerts so that the right people receive an email or SMS when a bot fails, when a queue reaches a critical backlog, or when a robot goes offline.
Orchestrator Roles and Permissions
Not everyone should have full access to Orchestrator. Define roles:
- Administrator: Full access — create, deploy, monitor everything
- Developer: Can publish packages and test in development environments
- Operator: Can monitor bots and manage queues but cannot deploy
- Business User: Can trigger specific attended bots only
Summary
The Orchestrator is the nerve centre of any RPA operation. It manages robots, deploys processes, schedules triggers, distributes work through queues, stores configuration assets securely, and provides complete visibility through logs and dashboards. Without the Orchestrator, bots run in isolation with no central management, no audit trail, and no recovery from failure. For any organisation running more than a handful of bots, Orchestrator is not optional — it is essential infrastructure.