Concurrency control breaks flow

[kingslowpoke]

Hi. 

 I have a process where I need to create excel file based on user selected rows from Dynamics using when record is selected. Everything works fine until I turn on the concurrent runs feature and limit it 1. Process generates 2 rows per record and I need to have them in order so this is a must if multiple rows have to be run. Otherwise generated order would be 1-1-2-2 instead of 1-2-1-2.

But turning concurrency control on makes the flow unable to return dynamic values. When a record is selected just stops returning anything. 

Any ideas how to fix this? Or is there something about concurrent runs that I am just not getting? Another way to set run order would be nice aswell.

[rohsh354]

Hello,

I am able to reproduce this issue. When concurrency control is OFF, and I trigger the flow from model driven app, it ask for the field inputs which I defined in my flow trigger as shown below:

When concurrency control is ON, then this text input is ignored due to which the trigger returns 0 records.

You should consider opening a Support Ticket with Microsoft Support, to get this investigated further and get it fixed.

Links:

https://powerapps.microsoft.com/en-us/support/

https://docs.microsoft.com/en-us/power-platform/admin/get-help-support

Hope this helps !

[kingslowpoke · Accepted solution]

Hi, 

It started working again by itself after 30 minutes or so with the concurrent runs still on. 😅

[Microsoft101]

I can confirm that turning concurrency control on also broke the "On Power BI Button Clicked" trigger on my flow. Same issue where the entity is returning blank. It won't let you turn the concurrency back off even if you delete the trigger entirely.

I just ended up remaking my flow and hoping two people don't use it at once.

Thanks