- Get started
- Build
- HTTP Request
- How connector nodes work
- Create a connection
- Sales and customer relationships
- Customer support and help desk
- Messaging and meetings
- Email
- Marketing
- Social media
- Files, documents, and e-signature
- Projects, collaboration, and code
- People and recruiting
- Finance and commerce
- AI models and agents
- Speech, vision, and language
- Data and location
- Cloud, identity, and security
- Deploy and run
- Examples
- Reference
Convert to Maestro Orchestrate
When a Maestro Automate workflow should convert to Maestro Orchestrate, what changes when it does, and how to convert it without rebuilding it.
Most workflows stay in Maestro Automate. When a workflow's design calls for more, such as runs that wait for days, you can convert it to Maestro Orchestrate, the UiPath product for long-running business processes. Converting is optional and isn't a rebuild: the workflow file stays the same, and you can convert it back.
When to convert
Convert a workflow when one of these applies. If you're planning a new process, the same list tells you where to start: in Maestro Orchestrate when one of these applies, and in Maestro Automate otherwise.
- 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 Business Process Model and Notation (BPMN) or Case 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.
What changes
| 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 API.
The work a run calls, the traces of that work, and audit events are kept the same way in both products. How long run data is kept describes their retention settings.
Runs of a converted workflow are priced as Maestro Orchestrate runs. Pricing describes Maestro Automate pricing.
Convert a workflow
- Open the workflow on the canvas.
- In the bottom toolbar, select the product menu. It shows Maestro Automate, and in Studio Web it's labeled Build as.
- Select Maestro Orchestrate, "Orchestrate a business process across agents, humans, and systems".
The workflow keeps its nodes and settings. To convert it back, select Maestro Automate in the same menu. Deploy the workflow again for the change to apply to its runs.
Until Maestro Automate runs have a section of their own, they appear as Maestro Flow processes in Maestro's instance management, together with Maestro Orchestrate runs.
Next steps
- Limits and fair use: the limits that apply to Maestro Automate runs.
- Deploy a workflow: deploy the converted workflow.
- Maestro Orchestrate or Maestro Automate?: the full comparison of the two products, in the Maestro Orchestrate guide.
- Maestro Automate or API workflow: another choice to make for short, API-only work.
- Community: ask questions and share workflows with other builders on the UiPath Forum.