For Each not working in parallel

[asonzini]

I have made a simple flow that, every time a new item is added to a list, sends an adaptive card to 2 individual users user to request information, and updates the element with the recieved information:

When items are added in quick succession to the list and get grouped inside the When an Element is Created, the For Each step will publish the cards for the first element, but will wait untill both cards have been answered in order to publish the cards for the subsequent element. The flow works properly when adding items slowly to the list, running one instance of the flow for each element. 

How can I get the flow to publish the cards for all items simultaneously?

[creativeopinion · Accepted solution]

@asonzini I don't believe you need a parallel branch in your case. Can you share a screenshot of your flow in the Classic Designer with all your actions expanded?

You can turn on the concurrency control in the Apply to Each action and set a threshold. By adjusting the logic of your flow, you should be able to just run a single set of these actions (instead of duplicating the actions in a parallel branch.

Is the adaptive card being sent to the same two users each time? Or does it differ based on the item created?

In the meantime, you might find this YT Tutorial helpful: 3 Mistakes YOU 🫵 are Making with the Apply to Each Action in your Microsoft Power Automate Flow

In this video tutorial I’ll go over how to avoid these common mistakes when using the Apply to Each action in a Power Automate flow:

1️⃣ Looping through a Single Item

2️⃣ Creating Unnecessary Nested Loops

3️⃣ Looping through an Unfiltered Array

At the end of the video I share a few helpful insights when it comes to using the Apply to Each action in your flow.

IN THIS VIDEO:

✅ How to avoid the Apply to Each action with a single item array

✅ How to use the item() function to access dynamic content in an array

✅ How to prevent unnecessary nested Apply to Each action loops

✅ How to use the Select action

✅ How to convert an array to a string with the Select action

✅How to use the Filter Query field

✅ How to count the number of items in an array

✅ How to use a condition control

✅ How to use the concurrency control

✅ How to set a top count

✅ How to use Compose actions for troubleshooting

Hope this helps!

If I helped you solve your problem—please mark my post as a solution ✅.
Consider giving me a 👍 if you liked my response!

👉 Level up your Power Automate skills by checking out my tutorials on YouTube
👉 Tips and Tricks on TikTok and Instagram

[asonzini]

@creativeopinion The parallel branches are not the problem, they are necessary since each card is different and is sent to a different user, and the users change for every list item (I want 2 different cards generated for every list item).

The problem is that when several List Items are loaded to the trigger When an Item is Created, the For Each action will run them one after the other, instead of in parallel.

Concurrency control in the Apply to Each action may be the problem here. In your video you explain that by default it runs through the items in sequence.

However, the tooltip indicates that with Concurrency Control turned OFF the instances will run in parallel:

Now, in classic designer the tooltip indicates the opposite:

I will try turning concurrency control ON as you suggested