Answered

turn on the concurrency control in "apply to each" action result to variable's value mixed

(0) Share

Report

Posted on by Owen_sheng Microsoft Employee

I'm building a flow like this

In the apply to each action, I update the variables and send a email with a option. The variables are defined before "apply to each", and these variables will be sent in emails.

As we know, send a email with a option will not complete the flow until the reveiver take action. In order to make sure all people receive my email, I have turn on the concurrency control in "apply to each". And this result to all the emails have same variables.

How can I fix this.

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

StretchFredrik 3,395 Super User 2025 Season 2 on at

Like (1)

Report

what i do is to use compose steps instead of variables. Variables dont work inside concurrent running loops. 😃

If this solved your issue please mark the post as Solved.
Also, if you appreciated my answer, don't forget to give it a Thumbs Up 😃

Was this reply helpful? Yes No
Owen_sheng Microsoft Employee on at

Like (0)

Report

I can not understand. Can you explain the detail.

Was this reply helpful? Yes No
StretchFredrik 3,395 Super User 2025 Season 2 on at

Like (0)

Report

I'm guessing you are setting the value of your variables inside the concurrent running loop? Instead use a 'Compose' Action to write the value you are currently setting in the variable, that way the value will be correct for every item. Such as:

Was this reply helpful? Yes No