hartra344
commented
2 months ago Discussed with Rohitha, and it looks like concurrency can be on a trigger and a for each and behavior of each is different. Our description describes how it works for Trigger. Rohitha is working with us to get messaging for For Each.
Describe the Bug with repro steps
This my sample flow:
Array variable value:
Compose action:
Delay action:
Delay by 10 seconds.
Test results for V3 designer:
Scenario 1: Keep default setting: "Concurrency control" = off
Loop 1:
Loop 2 is 10 seconds later:
Loop 3 is 10 seconds later:
Conclusion: it's executed sequentially.
Scenario 2: flip setting: "Concurrent control" = on and Degree of parallelism is 20:
Loop1:
Loop2:
Loop3:
Conclusion: it's executed in parallel.
Repeat the same scenarios in v1 designer, and got same results.
Verdict:
In the default setting, "Concurrent control" is off, LA runtime executes actions sequentially;
When toggling "Concurrent control" on and set a Degree of parallelism to larger than 1, LA runtime executes actions in parallel.
It's a runtime behavior, not a designer behavior.
V1 description matches runtime behavior:
V3 description is opposite of runtime behavior. This is a v3 LA designer bug.
Concurrency control description should be same as v1
What type of Logic App Is this happening in?
Consumption (Portal)
Which operating system are you using?
Windows
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos
No response
Browser
[Chrome, Edge, Safari]
Additional context
No response