SPO List updated - kicks off two back to back instances of the flow

(0) Share

Report

Posted on by rputhoff

Hello,

I've created multiple flows before, and recently a couple flows I've been working on kick off two instances of the flow (second one kicks off a minute after the first). I've put several checks within the flows to ensure that it doesn't kick off subsequent instances. I've also changed the flows to use the 'when an item is modified' trigger instead of 'when an item is created or modified.' I've also tried to put in Trigger Conditions in the settings. These were suggestions I found, but none of them worked.

The first flow doesn't even get to finish before the second one kicks off.

Anyone have this issue and find a solution that works? Almost every post I found did not have a resolution. Hoping someone here has found something that works.

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

SudeepGhatakNZ 14,394 Most Valuable Professional on at

Like (0)

Report

Go to the trigger settings of your flow, and enable "Concurrency Control," setting the degree of parallelism to 1. This will ensure that only one instance of the flow runs at a time, and subsequent triggers will queue until the first one completes.

Was this reply helpful? Yes No
ivan_apps 2,187 Moderator on at

Like (0)

Report

Is the SPO list updated via native sharepoint form or a power app? I’ve run into this when 2 quick updates are made (in my case 2 FormSubmit() events) in quick succession or when one field auto-saves and the second field is quickly entered. Check out the list audit history for clues on the updated item.

my solution was to either reduce form submits in the power app when no operation was done, or check for the version number of the list item. In my case I was looking for a creation event, which would be version 1.0, any other update is 2.0 or greater.

Was this reply helpful? Yes No
rputhoff 6 on at

Like (0)

Report

Hello,

Unfortunately that did not work to set the concurrency to 1. It actually held up our processes as it restricted the flows that could kick off for the entire SPO list. I need to restrict how many times a flow can kick off for one item in the SPO list at a time essentially.

This is a native SPO list. Not using Power Apps. I'm guessing it's auto-saving and kicking off a flow when a field is changed and then when they exit grid view and fully save the item. How would I reduce the number of form submits? Is there a way to turn off auto-save?

Thanks!

Was this reply helpful? Yes No