Cancel or resubmit flow runs in bulk
You can cancel or resubmit your flow runs in bulk instead of one at a time, which can be a huge time saver.
Resubmit flow runs
You can resubmit previous runs of a flow in bulk. To do this, follow these steps:
Sign in to Power Automate.
On the left panel, select My flows.
On the right panel, select the cloud flow that you want to resubmit or cancel.
Select All runs.
Tip
- The flow must have runs to cancel or resubmit the flow runs.
- You can resubmit or cancel up to 20 flows at a time.
On the Run history page, select the flow runs that you want to resubmit or cancel.
Select Resubmit flow run(s).
Important
The number of flows that you can resubmit is limited based on the maximum number of API calls for the connectors in the flow.
Cancel flow runs
You can cancel flow runs on the related flow's Run history page, or by using a template. The bulk cancel feature available through the flow portal is most efficient when you cancel up to 20 flows at a time. We recommend that you use the template linked previously in this section for more than 20 runs when possible. This also applies to runs in the hundreds. Alternatively, you can use the bulk cancel feature for all flows in Waiting or Running status regardless of the count. To set an expectation of how this utility functions review the following details.
Cancel flow runs in bulk on the flow 'Run history' page
To cancel flows, navigate to the flow portal and select My flows.
Next to the flow, select the ellipses (…) > Run history.
Alternatively, you can select the flow name > All runs from the 28-day run history list.
You can manually select up to 20 flows that are in Waiting or Running state.
To initiate the bulk cancellation feature instead, select Cancel all flow runs in the Run history menu at the top of the screen.
After you select Cancel all flows, a message appears asking you to initiate the bulk utility. Select Yes. If you're concerned about further unwanted flow runs being initiated, you can turn off the flow.
If there are more than 20 flows in Waiting or Running status, another message might appear to indicate that it might take several minutes for the flow run statuses to change to Canceling. This message means your flows are suspended, and no further actions are executed for flows that are already Running. Flows in Waiting status are also terminated without actions being executed.
Get the updated status changes in the run history list by periodically refreshing your browser screen.
Note
- Flows in the Running state are suspended and change to a state of Canceling before eventually changing to Canceled.
- This process can sometimes take up to 24 hours more more.
- In this scenario, the flows are suspended, and no further actions are executed.
- If you select a flow run in the Canceling state, it might appear that the spinner near an action is in motion, but it's in a suspended state. When flows are actually running, a notification banner diplays to indicate your flow is running. This isn't the case for suspended flows in the Canceling state.
The following screenshot shows the banner when a flow is running. A suspended flow in the Canceling status doesn't contain this banner.
Flows that exceeded the concurrency setting might be visible in the Waiting state alongside other flow runs in the Canceling state. This is by design. The flows were suspended when the bulk cancel was submitted unless they were triggered after the feature was used. The state changes to Canceling when their turn to be processed comes up in the queue.
You can ensure that flows in the Running or Waiting state before submitting a bulk cancel request were suspended and eventually change to the Canceled state.