Answered

is there any way to remove "Concurrency Control" from a flow once it is set

(0) Share

Report

Posted on by samjalloul

Hello -
The "Concurrency Control" has been set on the recurring trigger of a workflow. It says that " Limit number of concurrent runs of the flow, or leave it off to run as many as possible at the same time. Concurrency control changes the way new runs are queued. It cannot be undone once enabled."
Is there any way to get a copy of this flow without the concurrency setting turned on?

I tried "Save as" but that didn't work

-much thanks.

Categories:

Using flows

I have the same question (0)

All responses (7)

Answers (1)

v-litu-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @samjalloul,

You could set Degree of Parallelism to1, and then it will work like turning off "Concurrency Control".

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
Verified answer

samjalloul 23 on at

Like (8)

Report
Copy link

Link copied!

Thank you for your repose. Unfortunately, it does not solve the issue as the trigger still has "concurrency control" and that comes with many limitations. E.g. can't replace the trigger with a manual trigger or make the flow a child flow.

I have been able to find a fix on my own.

Should anyone else need this:
1- Export your flow to a zip package. (from flow details page, click export on top bar)
2- Open the package. Inside that package, find the file "definition.json" and open it with a json editor
3- Remove the recurrence node. It is under object > properties > definition > triggers > (type of trigger you have > runtimeConfiguration
4- save and import back into Power Automate as a new workflow.

You know have a copy of the workflow that does not have "concurrency control".

Was this reply helpful? Yes No
steve_hendy 385 on at

Like (0)

Report
Copy link

Link copied!

Thank you you just saved me a ton of work.

Was this reply helpful? Yes No
ericwhitley 137 on at

Like (0)

Report
Copy link

Link copied!
samjalloul,

I've been trying your method but getting an error when trying to Import the new package: "Something went wrong. Please try again later."

I found the triggers section of the definition.json file:
"triggers": { "When_an_event_is_added,_updated_or_deleted_(V3)": { "splitOn": "@triggerOutputs()?['body/value']", "metadata": { "operationMetadataId": "1a4fd861-1448-4c7e-863d-48fc1b768d4a" }, "type": "OpenApiConnectionNotification", "inputs": { "host": { "apiId": "/providers/Microsoft.PowerApps/apis/shared_office365", "connectionName": "shared_office365_1", "operationId": "CalendarGetOnChangedItemsV3" }, "parameters": { "table": "AAMkAGY0OGM1NzAxLWM0MDgtNGQyZS1hYjRmLWZkYmNkNTg4NGJkNgBGAAAAAACZgLMZjD2dSLFbjY4M1Po1BwBSd3CgKSmtRpFT5mnca_o-AAAAAAEGAABSd3CgKSmtRpFT5mnca_o-AAIBNOp9AAA=", "incomingDays": 90, "pastDays": 3 }, "authentication": "@parameters('$authentication')" }, "runtimeConfiguration": { "concurrency": { "runs": 50 } } } },
and remove these lines:
, "runtimeConfiguration": { "concurrency": { "runs": 50 } }

Then I Re-Zipped the files, tried to import and got the error. I'm thinking my edit to the json file was incorrect.

Then I tried it by removing the runtimeConfiguration node from the Tree view. Then saving the Json file, reZipping and uploading. Got the error again.

Just to confirm, I tried Uploading the original zip file (without modifying the definition.json file) and it worked. So the only difference is the change to the json file.

What am I doing wrong?

Thanks

Was this reply helpful? Yes No
ericwhitley 137 on at

Like (0)

Report
Copy link

Link copied!

Hi Steve, what's the trick to editing the definition.json file? I've tried it a couple of ways and I get errors when trying to Upload the zip file.

What exactly should I be removing?

Thanks

Was this reply helpful? Yes No
steve_hendy 385 on at

Like (0)

Report
Copy link

Link copied!

You can't. Just move the degree of parallelism slider to 1 as mentioned above.

Was this reply helpful? Yes No
uhdacarter 2 on at

Like (0)

Report
Copy link

Link copied!

Perhaps the problem is introduced when you first Export the Flow. While the "Export Package" page is up (where you can specify Name, Environment, and Description), there is a section below called "Review Package Content".
The columns in that section are labelled "NAME", "RESOURCE TYPE", "IMPORT SETUP", and "ACTION".
You may notice that "Import Setup" has a link that reads "Update". Click that link and select "Create as New", click "Save", then "Export". This is untested - so proceed at your own risk.

Was this reply helpful? Yes No