cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Regular 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
Highlighted
Super User II
Super User II

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

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

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

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
secondImage

August 2020 CYST Winners!

Check out the winners of the recent 'Can You Solve These?' community challenge!

thirdImage

Experience what's new for Power Automate

Join us for an in-depth look at the new Power Automate features and capabilities at the free Microsoft Business Applications Launch Event.

firstImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

Top Solution Authors
Top Kudoed Authors
Users online (3,411)