Hello,
I have a flow that makes an http patch request to Graph API on an email item.
it's located in an apply to each where a variable is used as a trigger to avoid next runs of the loop to not apply further actions...
Then my apply to each needs to be setup in a sequence and not in parallel for that trigger to work correctly.
I have a failed run where the patch has failed because of modification key beeing changed before the change has applied.
It makes me think the apply to each has applied in parallel and not in sequence... and a second loop has applied a change before the first did so.
Finally looking at the description of this action in the legacy Designer:
each loops execute sequentially by default. Override the default setting to customize the degree of parallelism.
And looking at the description in the new designer:
By default, Logic App instances run at the same time, or in parallel. This control changes how new runs are queued and can't be changed after enabling. To run as many parallel instances as possible, leave this control turned off. To limit the number of parallel runs, turn on this control, and select a limit. To run sequentially, select 1 as the limit.
So which assesment is true ? default behavior is sequential or parallel in apply to each ?
is the behavior different if I save from old or new designer ?
I guess turning on and selecting "1" as a degree of parallelism stick it as sequentially anyway.
But in other older flows I have those loops that needs to be run sequentially as well and that have the trigger turned off. So I'd like to be aware of any change in the default behavior of that action...
Thanks
