- 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.
- Audit, compliance, or service-level management needs the full record of every run for as long as the process matters.
- More than 50 runs happen at the same time, routinely.
- Runtime governance beyond platform policy is required, such as output provenance or a tamper-evident audit.
- 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 run traces and logs are kept | 30 days | A period you configure |
| 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.
- Monitoring dashboards, incidents, and alerts.
- Process optimization dashboards.
- Run data through the Maestro Orchestrate API.
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.