Skip to main content

Notifications

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Power Platform Community / Forums / Building Flows / SPO List updated - kic...
Building Flows
Suggested answer

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

(0) ShareShare
ReportReport
Posted on by rputhoff 4
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:
Business Process Flows
  • rputhoff Profile Picture
    rputhoff 4 on at
    SPO List updated - kicks off two back to back instances of the flow
    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!
  • ivan_apps Profile Picture
    ivan_apps 2,187 on at
    SPO List updated - kicks off two back to back instances of the flow
    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. 
  • Suggested answer
    SudeepGhatakNZ Profile Picture
    SudeepGhatakNZ 13,677 on at
    SPO List updated - kicks off two back to back instances of the flow
    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.
     

Helpful resources

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Welcome to the Power Platform…

We are thrilled to unveil the newly-launched Power Platform Communities!…

Community Update 9/9/24…

Power Platform Community Update…

Welcome to the new Power Platform Community!…

We are excited to announce our new Copilot Cookbook Gallery in the Community…

more Community News

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 140,640

#2
RandyHayes Profile Picture

RandyHayes 76,308

#3
Pstork1 Profile Picture

Pstork1 63,336

Leaderboard

Featured topics

Product updates

Microsoft Power Platform Community release plans