cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

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
Super User

Hi @Anonymous 

 

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
Super User

Hi @Anonymous 

 

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
2022 Release Wave 1 760x460.png

2022 Release Wave 1 Plan

Power Platform release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

Top Solution Authors
Users online (1,688)