Automation Orchestration
Automation Orchestration enables you to automatically route execution from one automation to another based on RPA robot status and predefined business rules. It provides a centralized way to coordinate automation execution without adding routing logic to individual automations.
Unlike scheduler-based execution, which starts an automation at a predefined time or interval, Automation Orchestration responds to the status of a preceding RPA execution. For example, when a robot completes or fails, an orchestration rule can determine what should run next, creating automation sequences where the status of one execution determines the next execution path.
Automation Orchestration vs. Scheduler
The primary difference is what determines when the next automation runs:
Execution Methods
| Execution Method | How It Works | Example |
|---|---|---|
| Scheduler | Starts an automation at a configured time or interval. | Run an invoice-processing bot every day at 9:00 AM. |
| Automation Orchestration | Routes execution based on the status of a preceding RPA robot and the configured business rules. | When an invoice bot completes, trigger another RPA bot or a Robility Flow. |
Use Scheduler when an automation needs to run on a fixed schedule. Use Automation Orchestration when the next execution depends on the status of another automation.
What You Can Do with Automation Orchestration
a. Route execution from one RPA robot to another RPA robot.
b. Route execution from an RPA robot to a Robility Flow.
c. Define different execution paths based on configured conditions.
d. Define a fallback path when none of the configured conditions are satisfied.
e. Centralize routing logic instead of implementing it separately in individual automations.
f. Connect multiple automation steps into a coordinated execution sequence.
How Automation Orchestration Works
Automation Orchestration uses the Robility Business Rule Engine (BRE) to evaluate configured rules and determine the next execution target.
The routing process is:
1. Monitor Robot Status – Automation Orchestration monitors the selected robot’s status from the Automation Ops page.
2. Trigger the Rule – When the robot reaches the configured trigger status, the associated rule is triggered.
3. Evaluate Conditions – The BRE evaluates the conditions configured for the rule.
4. Route Execution – When a condition is satisfied, execution is routed to the configured RPA or Robility Flow target.
5. Apply Fallback – If no condition is satisfied, the ELSE path routes execution to the configured fallback destination, when available.
Configuring a Rule
1. Define Rule Details
a. Open Automation Orchestration and click + Create New Rule.
b. Enter a unique Rule Name.
c. Enter a Description, if required.
The rule name identifies the rule, while the description provides context about its purpose and routing logic.
2. Configure the Trigger
Trigger Configuration defines when the rule should be evaluated.
a. Under Trigger Configuration, select RPA (currently the only supported trigger type — see Availability table below).
b. Select the required Trigger Event.
c. Select the Robot to monitor.
Automation Orchestration uses the selected robot’s status from the Automation Ops page to determine when the trigger event occurs. For example, if Robot Completed is selected, Automation Orchestration checks the robot’s status and, once it reaches Completed, triggers the rule and evaluates its conditions.
Trigger Types
| Trigger Type | Availability | Description |
|---|---|---|
| RPA | Supported | Uses the selected RPA robot's status from the Automation Ops page to trigger rule evaluation. |
Note: Robility Flow is currently disabled and cannot be used to trigger a rule.
Trigger Events
| Trigger Event | Description |
|---|---|
| Robot Completed | Triggers when the selected robot completes execution. |
| Robot Started | Triggers when the selected robot starts execution. |
| Robot Failed | Triggers when the selected robot encounters an execution failure. |
| Robot Cancelled | Triggers when the selected robot execution is cancelled or stopped. |
3. Configure the Action
Action Configuration defines what happens once the trigger and its conditions are satisfied. Under Action Configuration, select RPA or Robility Flow.
a. For RPA, select the target robot using Select Robot.
b. For Robility Flow, select the target Flow and version using Select Flow.
Action Types
| Action Type | Availability | Description |
|---|---|---|
| RPA | Supported | Routes execution to the selected RPA robot. |
| Robility Flow | Supported | Routes execution to the selected Robility Flow. |
Note: Send Notification and Custom Action (API/Webhook) are not currently supported — both are visible in the interface but cannot currently be configured as a rule action.
4. Save the Rule
Click Save to save the rule, or Cancel to discard changes.
Once saved, Automation Orchestration monitors the configured robot status and evaluates the rule when the trigger event occurs.
Note: Automation Orchestration checks the Automation Ops page every minute for the configured robot status. During this monitoring period, the automation cannot be deleted or disabled.
Accessing Automation Orchestration
The Automation Orchestration screen displays all existing rules and provides access to create new ones. The rules list includes:
Rule List
| Column | Description |
|---|---|
| Rule Name | Name assigned to the rule. |
| Status | Current status of the rule. |
| Description | Brief description of the rule and its routing logic. |
| Updated On | Date and time when the rule was last modified. |
Use Search rules by Rule Name to locate an existing rule. If none exist, the table displays “No Records Found.” Click + Create New Rule to create one.
Use Cases
Sequential Invoice Processing — RPA Robot A enters invoice data into an ERP system. When it completes, the rule routes execution to RPA Robot B, which validates the invoice data — so validation starts automatically after entry finishes.
RPA to Robility Flow Processing — An RPA bot collects customer information from a business application. On completion, the rule routes execution to a Robility Flow that performs additional processing, such as API integration or multi-system workflow execution, allowing RPA and Robility Flow to work together in one business process.
Failure-Based Routing — An RPA automation processes a batch of documents. If it completes, the rule routes to the next RPA automation; if it fails, the rule routes to a Robility Flow configured for exception processing — giving each outcome a defined execution path.
Limitations
1. RPA is currently the only supported trigger type; Robility Flow cannot be used as a trigger.
2. Routing currently supports RPA → RPA and RPA → Robility Flow only.
3. Human-in-the-Loop (HITL) routing is not currently supported.
4. Send Notification and Custom Action (API/Webhook) are not currently supported as actions.
5. Unsupported trigger and action options may be visible in the interface but cannot currently be configured.
6. Additional trigger and action types may be introduced in future releases.
