Answered

Concurrency Control turned off when cloud flow is published

(4) Share

Report

Posted on by bbains

I'm working with cloud flows within a solution. Recently (last 2 weeks) I have noticed that the Concurrency Control I've turned on for Apply to Each Actions is being turned off when I Publish the flow after making changes. Has anyone else experienced this behavior?

his?

PA Concurrency turned of when save or publish.png

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (1)

Sort by

DR-26070948-0 3 on at

Like (1)

Report
Copy link

Link copied!

I have the same issue. Have you found a solution to this yet?

Was this reply helpful? Yes No
Verified answer

sigmandel_rimac 8 on at

Like (2)

Report
Copy link

Link copied!
I did some tests and found that it's a web UI issue. The concurrency setting is always shown as "off" only when using the new designer.

It's actually very severe because you don't need to publish it. If you edit anything (even if you don't edit the for-each step) and save it, it will save the flow with concurrency off! That can be confirmed by refreshing the web page after saving; it will show as "off".

That's how I found out after making a little change to one of my critical flows just to later discover later that the flow was broken. I tried many things including reimporting the flow from a saved package, yet because I was using the new designer, it kept showing as "off".

To fix:
edit it using the old designer.
turn on concurrency.
save it.

Was this reply helpful? Yes No
bbains on at

Like (1)

Report
Copy link

Link copied!

sigmandel_rimac's answer identifies and corrects the issue. I'm adding a little for info based on my experience. New designer definitely shows concurrency as "off" when you open a flow and click on a control with the concurrency property. What I have noticed is that I can turn the setting back on, select a different action in the flow, and then save and publish the flow, the concurrency setting gets saved as on. This observation is based on the fact that flow execution time is in line with run times when concurrency is "on" after doing this.

Was this reply helpful? Yes No
Suggested answer

CU02081222-1 2 on at

Like (2)

Report
Copy link

Link copied!

The issue should be fixed and rolled out on 8/9.

Was this reply helpful? Yes No