In some cases it can be helpful to avoid parallel runs of a flow.
An example of a real life scenario
For a project that uses Dataverse and model-driven apps, we are using the out of the box Tasks.
A table “Task” exists by default in a Power Platform environment with a Dataverse database.
A flow automatically generates tasks linked to another table record.
Another automatic flow reacts on changes in the Task table, in other words when a task status is completed.
When we have two open tasks, the user can very quickly complete these two tasks. It could lead to two parallel flow runs.
If this flow changes the status of a record, it could result in conflicts because one task changes the status and another one as well.
This could be a use case where you want to deactivate parallel flow runs.
How to disable parallel flow runs
To disable parallel flow runs, you can open the settings of the trigger.
First turn “Concurrency control” on. Second change the degree of parallelism to 1.
