- Introduction
- Getting started
- Build on any canvas
- Build with Case
- Reference
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Build with Flow
- Build with BPMN
- Operating
- Monitoring
- Optimizing
- Reference information
Maestro Orchestrate or Maestro Automate?
How to choose between Maestro Orchestrate, for long-running business processes, and Maestro Automate, for workflows that finish within 24 hours.
UiPath Maestro comes as two products, and both build on the Flow canvas:
- Maestro Orchestrate orchestrates long-running business processes across agents, humans, and systems, on the Case, Flow, and BPMN canvases.
- Maestro Automate builds workflows in which AI agents and APIs work together, and each run finishes within 24 hours. What is Maestro Automate? introduces it.
Choose Maestro Orchestrate when
Choose Maestro Orchestrate when one of these applies:
- The process waits on a human or an external event for more than a day.
- Someone must act on a run while it's in progress: pause it, resume it, migrate it to a new version, or move it to a different step.
- You need a run in Maestro more than 30 days after it ends, for example to look back at it for an audit or a compliance review.
- More than 50 runs happen at the same time, routinely.
- The process needs the Case or BPMN canvas.
Examples are order-to-cash, claims processing, employee and customer onboarding, procure-to-pay, product recall, and Know Your Customer (KYC) and compliance case handling.
Choose Maestro Automate when
Choose Maestro Automate when none of the cases above applies: each run finishes within 24 hours, up to 50 runs happen at the same time, and 30 days of run history is enough.
Compare them
| Maestro Automate | Maestro Orchestrate | |
|---|---|---|
| How long a run can last | 24 hours | No limit, so a workflow can wait days and continue where it stopped |
| Runs at the same time | 50 | No limit |
| How long a run is kept in Maestro | 30 days after the run ends | 30 days by default. An administrator can set 1 to 180 days. |
| Canvases | The Flow canvas | The Case, Flow, and BPMN canvases |
Maestro Orchestrate also adds these controls and views for runs:
- Pause and resume a run.
- Migrate a run to a new version.
- Go to a specific step in a run that's in progress.
- The Monitoring tab in Maestro, with monitoring and incident dashboards and alerts. It leaves out the runs of Maestro Automate versions, even when the same process also has Maestro Orchestrate versions.
- Process optimization dashboards.
- Run data through the Maestro Orchestrate API.
Run history, traces, and logs
Only how long Maestro keeps the run in Instance management depends on the product. The job of the run in Orchestrator, traces, the jobs of the work a run calls, and audit events are kept the same way in both products.
The process data retention policy in Orchestrator keeps completed jobs for 30 days by default. An administrator can set it from 1 to 180 days.
| Data | Maestro Automate | Maestro Orchestrate |
|---|---|---|
| The run in Instance management in Maestro | Deleted 30 days after the run ends | Set by the process data retention policy |
| The job of the run in Orchestrator, with its logs | Set by the process data retention policy | Set by the process data retention policy |
| Traces | Traces of the work the run calls: 90 days by default, or 1 or 7 days set by an administrator | 90 days by default, or 1 or 7 days set by an administrator |
| Jobs of the agents, RPA workflows, and other automations a run calls | Their own retention settings | Their own retention settings |
| Audit events | Captured the same way in both products | Captured the same way in both products |
| Monitoring history | No Monitoring tab | Kept in Insights |
These pages describe the retention settings:
- Time-To-Live enforcement for Trace data in the Automation Ops guide: the AI Trust Layer policy setting that sets how long traces are kept, 90 days by default.
- Process data retention policy in Orchestrator: how long jobs and their logs are kept, and how long Maestro Orchestrate keeps a run in Instance management.
- Audit logs, Insights ingestion, and retention: how long audit logs and monitoring history are kept.
To keep traces and audit logs outside UiPath, an organization administrator can stream them to your own destination with Data Export. The export isn't affected by these retention settings.
The Monitoring tab in Maestro, on the page of a process, isn't the Monitoring tab at the top of Orchestrator.
Switch a workflow between them
A workflow built on the Flow canvas can move between the two products without a rebuild. In the bottom toolbar of the canvas, the product menu, labeled Build as in Studio Web, offers Maestro Orchestrate and Maestro Automate. The workflow keeps its nodes and settings, and you can switch it back. Deploy the workflow again for the change to apply to its runs.
Convert to Maestro Orchestrate in the Maestro Automate guide describes the steps.
Next steps
- Choosing a canvas: choose between Case, Flow, and BPMN.
- What is Maestro Automate?: the short-running workflow product.