cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
JC_2020
Frequent Visitor

Power automate not returning collection to power apps when concurrency control is limited to 1

Hi - Not sure if anyone else has heard of this issue.  I am trying to use concurrency control to limit my flow runs to 1 at a time.  I need to do this since the flow is updating a data source, and then pulling data from the same data source.  I have a work around in the flow so the results match the input the that was entered (using "user" and another unique id).  This will be inefficient and not userfriendly if the userbase grows.

 

I tried turning on conccurrency control and limiting it to 1.  The app no longer gets a response from power automate.  When looking at the runs, all the data is being processed and supposedly responding to the app.  I then tried creating a brand new app and new flow (typical work around when there are "glitches" with power app solutions) and the still nothing.

 

Is there an existing bug for this scenario, a documented work around, or is this a "feature"?

 

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
manuelstgomes
Super User II
Super User II

Hi @JC_2020 

 

Each Power Automate run should be considered as atomic, meaning that they can fire multiple times and work concurrently depending on the trigger. The behavior is good and bad because if you want to update something atomically sequentially, it won't work. 

 

As far as I know, there's no concept of a queue, where the Power Automates are submitted and parsed one by one.

 

Sorry for the bad news, but this is the intended behavior.

 

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Cheers
Manuel

View solution in original post

1 REPLY 1
manuelstgomes
Super User II
Super User II

Hi @JC_2020 

 

Each Power Automate run should be considered as atomic, meaning that they can fire multiple times and work concurrently depending on the trigger. The behavior is good and bad because if you want to update something atomically sequentially, it won't work. 

 

As far as I know, there's no concept of a queue, where the Power Automates are submitted and parsed one by one.

 

Sorry for the bad news, but this is the intended behavior.

 

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Cheers
Manuel

View solution in original post

Helpful resources

Announcements
Process Advisor

Introducing Process Advisor

Check out the new Process Advisor community forum board!

MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

Users online (27,979)