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 initiated by instant triggers

Administrators can enable users to resubmit flow runs initiated by instant triggers. Instant triggers, which are used to manually start flows, can be activated through Power Automate, a mobile app, or a button in a canvas app, among other methods.

There are two options to enable flow run resubmission for flows initiated by instant triggers, which are through Power Platform admin center and by using PowerShell.

Power Platform admin center

1. Sign in to your Power Platform admin center account.
2. Select Settings and then search for Power Automate flow run resubmission.
3. Choose whether to enable or disable the functionality using the toggle.

Apply tenant setting using PowerShell prerequisites

To perform the administration operations in the cmdlets, you need the following:

• Any of these roles from Microsoft Entra ID: Tenant admin, Power Platform administrator, or Dynamics 365 Service Administrator. These roles can access the Power Apps admin PowerShell cmdlets without requiring a Power Apps plan for administrative access. However, these administrators need to sign in to the Power Platform admin center at least once before using the PowerShell cmdlets. If this isn't done, the cmdlets fail with an authorization error.

• Power Platform administrator or Dynamics 365 administrator permissions are required to search through another user's resources. Environment admins only have access to those environments and environment resources for which they have permissions.

• For Dataverse for Teams environments, you must be a Power Platform administrator to manage environments where you aren't the owner of the team in Microsoft Teams.

1. Sign in to your tenant account:

 Add-PowerAppsAccount -Endpoint "prod" -TenantID <Tenant_ID>

1. Retrieve and store your tenant settings in TenantSettings:

 $tenantSettings = Get-TenantSettings

1. Set the powerPlatform.powerAutomate.disableFlowRunResubmission flag to False, to allow flow run resubmissions for cloud flows initialized by instant triggers.

 $tenantSettings.powerPlatform.powerAutomate.disableFlowRunResubmission= $False
 Set-TenantSettings -RequestBody $tenantSettings

Learn more about PowerShell commands in PowerShell support for Power Apps and Power Automate.

Resubmit flow runs

You can resubmit previous runs of a flow in bulk. To do this, follow these steps:

1. Sign in to Power Automate.

2. On the left panel, select My flows.

3. On the right panel, select the cloud flow that you want to resubmit or cancel.

4. 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.

5. On the Run history page, select the flow runs that you want to resubmit or cancel.

6. 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

The bulk cancel feature enables you to initiate the cancellation process for any flows in the queue that are currently in the Running or Waiting state, without needing to select individual flow runs. This is useful during incidents involving numerous erroneous flows. By using this feature, all flow runs in the queue are immediately suspended and are no longer processed. While suspended, their status displays as Waiting and systematically transitions to Canceling and finally to Cancelled.

Cancel flow runs in bulk on the flow 'Run history' page

1. To cancel flows, navigate to the flow portal and select My flows.

2. 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.

3. 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.

4. After you select Cancel all flows, a message appears asking you to initiate the bulk utility. Select Yes. Optionally, you might choose to select the checkbox to stop your flow and address any underlying issues that are triggering faulty runs. Any queued flows show as Waiting and don't clear until the flow is turned back on.

5. 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.
   • 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 displays to indicate your flow is running. This isn't the case for suspended flows in the Canceling state.

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. Bulk cancelation can be sped up by adjusting concurrency limits to (100), otherwise it slows the process even further. 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.