- Get started
- Build
- Deploy and run
- Deploy a workflow
- Monitor runs
- Retry and cancel
- Limits and fair use
- Examples
- Reference
Retry and cancel
What happens when a step fails, and the steps to open a run in Maestro, retry it from the failed step, or cancel it.
A deployed workflow runs without you, but you can still step in. When a run fails at a step, retry it from that step. When you don't want a run to finish, cancel it.
What happens when a step fails
When a node fails in a deployed workflow, for example because an app didn't respond, the run doesn't end. It pauses at the failed node and waits for you. In Maestro, its status is Faulted.
You then decide what happens next:
- Retry the run, when the failure was temporary, such as an app that was down for a moment.
- Cancel the run, when it shouldn't continue.
A paused run counts toward the 50 runs that can run at the same time, so don't leave failed runs waiting. Limits and fair use describes the limits.
Open a run
- Select the product launcher, the grid icon at the top left of any UiPath page, such as Studio Web, then select Maestro.
- In the left panel, select Flow instances, then select the name of your workflow. Its runs are listed on the Process instances tab.
- Optionally, to list only the failed runs, set the Status filter.
- Select the name of the run.
The run opens with the workflow on the canvas, the Execution trail of the steps that ran, and an Incidents tab with the error of the failed step. In Maestro, a run is called an instance.
To start from the error instead, select Flow incidents in the left panel. Monitor runs describes both lists.
Retry a run
Retry runs the workflow again from the step that failed. The steps that completed before it, such as the trigger, don't run again.
- Open the failed run.
- Select Retry at the top right.
- Optionally, add a Comment that explains why you retry the run.
- Select Retry instance.
A notification confirms the request. Only the failed step runs again:
- The Execution trail lists the new attempt below the first one. If it fails again, it has its own incident.
- Action history records who retried the run, when, and the comment, or "No comment provided".
If the step failed because of how the node is set up, such as a wrong URL, a retry fails the same way. Fix the node in the workflow, test it in debug mode, and deploy the new version. Troubleshooting lists the most common errors and their fixes.
Cancel a run
Canceling ends the run for good. You can't resume or retry a canceled run.
- Open the run.
- Select Cancel at the top right.
- Optionally, add a Comment that explains why you cancel the run.
- Select Cancel instance.
A notification confirms the request, and the run ends. The Execution trail keeps the record of the steps that ran, including the error of the failed step.
Next steps
- Monitor runs: follow runs and read what each step did.
- Handle errors: make a workflow recover from a failed step on its own, without a retry.
- Troubleshooting: fix the errors that make a step fail.
- Community: ask questions and share workflows with other builders on the UiPath Forum.