Respond to Power Apps with Limited Concurrency Flow

[KyleJ]

I am attempting to create a workflow that contains multiple different actions, which are all being triggered via various buttons in a powerapps, that all pass in a variable that is used in determining the outcome of a switch statement inside a flow. 

This flow is limited to a single instance (qued flow) because every time a flow is executed, I need to ensure qued flows are held until the first flow makes all changes. concurrent flows can break my process. 

for one portion, I need to know (In powerapps) once the flow has finished running. It should be within a couple seconds every time. 

I have set a variable in powerapps to the Run function. Example: Set(myVar,Run(...))

In Power AUtomate, i have used the "Respond to a Power App or Flow" Action. 
I added an output
I selected Yes/No (Because I am using a boolean, that will trigger a refresh inside powerapps once the flow completes, if true) 
and for testing, I simple used true.

When saving the flow, i am prevented from saving with FULL error code: 
Request to XRM API failed with error: 'Message: Flow client error returned with status code "BadRequest" and details "{"error":{"code":"InvalidOpenApiFlow","message":"Flow save failed with code 'InvalidConcurrencyConfiguration' and message 'The concurrency configuration of workflow trigger 'manual' of type 'Request' at line '1' and column '679' is not valid. The concurrency control is not supported when the workflow contains actions of type 'response' without the operationOptions flag set to 'asynchronous'.'."}}". Code: 0x80060467 InnerError: '.

I believe this is telling me I simply cannot reply to a Powerapp once the flow has been limited to 1 instance, qued. 
I don't understand why it would be able to respond. I can see that it some cases a user might be waiting, But I believe it's up to the developer to understand and work with that.

My flow should not be taking more than a second or two to run.
I need limited instances - I need 1 flow to complete before beginning the next. 
I need to respond to the powerapps trigger and let the user know of the completion. 

[Anonymous]

@KyleJ  were you able to get the workaround. i have similar requirement but limited concurrency is set to 1

[aware-ingo]

Same issue here. Any solutions?

[P3Sven]

You could work with Child Flows.

Manual triggering Parent Flow via Power Apps, respond Power Apps and after firing Child Flows, but incl. concurrency control.

[UrbanCog]

I have a similar issue to KyleJ.  I need a single instance of a flow to run, with requests getting queued and serviced one at a time.  The flow increments a number stored in a List and with concurrent flows, different flow instances are reading the List before the other flow has time to Update the Item with the new value, leading to the same number being used more than one.  This has worker safety implications, so obviously that's not acceptable.   

I built a parent flow with no concurrency setting, which calls a child flow with concurrency "Degree of Parallelism" set to 1, as P3Sven suggests, but the outcome is the same Code: 0x80060467 InnerError: noted above.

If there's no solution to this issue, it will severely limit the range of apps that can be configured in the Power Platform.

[dominikmad]

I have no clue if this helps anyone, but i had mostly a simular problem with the error code: "The concurrency configuration of workflow trigger 'manual' of type 'Request' at line '1' and column '749' is not valid. The concurrency control is not supported when the workflow contains actions of type 'response' without the operationOptions flag set to 'asynchronous'.\"."}}". Code: 0x80060467 InnerError: "."

This article helped a lot:

2 Concurrency options to better control speed in the Power Platform (sharepains.com)

What i did basically was, that I took the "send response" function and changed the settings to allow asynchronity: (screenshot is in the child flow)

[dominikmad]

please see my comment... i think it solves your problem

[SwJ23]

This worked for me, thank you. I will be spending more time clicking the ellipsis on each connector to see what options are available.