maestro-automate
latest
false
Maestro Automate user guide
- Get started
- Build
- Deploy and run
- Deploy a workflow
- Monitor runs
- Retry and cancel
- Limits and fair use
- Examples
- Reference
Limits and fair use
Maestro Automate limits: runs that finish within 24 hours, up to 50 runs at the same time per tenant, and runs kept for 30 days after they end.
Maestro Automate is built for short-running workflows that finish within minutes or hours. Use these limits as design guidance: plan each workflow to stay within them.
Design guidance
| Plan for | Guidance |
|---|---|
| How long a run lasts | Design each run to finish within 24 hours. |
| Runs at the same time | Up to 50 runs at the same time, per tenant. |
| How long a run is kept | Every step and value of a run is kept for 30 days after the run ends. |
A few patterns help you stay within them:
- Keep human steps short. A run that waits for a human should get an answer the same day. Human in the loop: escalation or human step has tips.
- Spread out large batches. If one event starts many runs at once, for example a file with hundreds of rows, process the rows in a Loop inside one run, or start the runs on a schedule.
- Save what you need to keep. If you need a run's results for longer than 30 days, write them to an app or a Data Fabric entity before the run ends.
Fair use
UiPath monitors usage against these limits. A run isn't stopped or failed because it goes over them. If your workflows routinely need longer runs, more runs at the same time, or a longer history, Convert to Maestro Orchestrate describes when converting fits.
Next steps
- Retry and cancel: retry a run that failed at a step, or cancel a run.
- Monitor runs: the run history and the trace of each run.
- How long run data is kept: the work a run calls, traces, and audit events.
- Pricing: how runs are metered and what the monthly allowance includes.
- Community: ask questions and share workflows with other builders on the UiPath Forum.