How to prevent a flow from executing twice while the first run is still processing

If your flow has a schedule as a trigger and it is possible for a run to take a longer time to process than the required time set in the schedule, the Concurrent Run Execution feature will assist.

It will let the first run complete processing first, so that there will only be one run processing in the flow. If the second run tries to process while the the first run is still processing, it will give a concurrent error.

To make this change to your flow, follow the below instructions.

  1. Click on “Details” on your flow as highlighted in the below image.


  1. Scroll down to the Concurrent Run Execution field and type “1” or use the top arrow and on the right of the field to increase it to 1 as illustrated below.

  1. Scroll to the top and click on “Save” to save this change and shown in the image below.