Merging changes synced from https://github.com/MicrosoftDocs/power-automate-docs-pr (branch live)

Author: Learn Build Service GitHub App

articles/how-tos-bulk-resubmit.md

@@ -6,7 +6,7 @@ author: DBEKI
 ms.service: power-automate
 ms.subservice: cloud-flow
 ms.topic: how-to
-ms.date: 02/19/2025
+ms.date: 05/23/2025
 ms.author: dbekirop
 ms.reviewer: angieandrews
 search.audienceType: 
@@ -95,7 +95,12 @@ You can resubmit previous runs of a flow in bulk. To do this, follow these steps
 
 ## Cancel flow runs
 
-You can cancel flow runs on the related flow's **Run history** page, or by using a [template](https://make.preview.powerautomate.com/galleries/public/templates/52c2eb66c0664b3b82480d1adcc6c1b4/cancel-all-of-my-flow-runs?environment=e85a08f2-6b04-ef9d-bbe3-05c8fb307b0b). 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.
+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**.
+
+  > [!TIP]
+  > - If a flow is turned off, pending canceled flows remain **Waiting**, and the queue doesn't clear until the flow is turned back on.
+  > - If the flow was throttled, allocate some [capacity](desktop-flows/capacity-process.md#allocate-process-capacity-to-a-cloud-flow) or the queue remains stuck and doesn't clear. Contact your environment administrator to assign capacity to the environment, which can be applied to the flow.
+  > - To expedite cancellation on flows with [concurrency](limits-and-config.md#concurrency-looping-and-debatching-limits) settings, adjust the setting to the maximum value (100) so erroneous queued runs can clear (100) at a time.
 
 ### Cancel flow runs in bulk on the flow 'Run history' page
 
@@ -108,15 +113,7 @@ You can cancel flow runs on the related flow's **Run history** page, or by using
 
     To initiate the bulk cancellation feature instead, select **Cancel all flow runs** in the **Run history** menu at the top of the screen.
 
-    :::image type="content" source="media/cancel-resubmit-how-to/flowrunlist.png" alt-text="Screenshot of the 'Cancel all flow runs' option.":::
-
-1. 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.
-
-    :::image type="content" source="media/cancel-resubmit-how-to/cancelprompt.png" alt-text="Screenshot of the 'Cancel all runs for this flow' message.":::
-
-1. 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.
-
-    :::image type="content" source="media/cancel-resubmit-how-to/workingonit.png" alt-text="Screenshot of the 'We're working on it' message that asks you to wait for a flow status.":::
+1. 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.
 
 1. Get the updated status changes in the run history list by periodically refreshing your browser screen.
 
@@ -126,11 +123,7 @@ You can cancel flow runs on the related flow's **Run history** page, or by using
     > - 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.
 
-The following screenshot shows the banner when a flow is running. A suspended flow in the **Canceling** status doesn't contain this banner.
-
-:::image type="content" source="media/cancel-resubmit-how-to/runningflow.png" alt-text="Screenshot of the banner that indicates a flow is running.":::
-
-Flows that exceeded the [concurrency](limits-and-config.md#concurrency-looping-and-debatching-limits) 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.
+Flows that exceeded the [concurrency](limits-and-config.md#concurrency-looping-and-debatching-limits) 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.
 
 :::image type="content" source="media/cancel-resubmit-how-to/wait-cancel.png" alt-text="Screenshot of flow runs in states of 'Waiting' and 'Canceling'.":::