Control concurrency in Apply to each to avoid throttling

1 min read Level: Intermediate

Tune Apply to each concurrency for faster flows without triggering throttling.

Click image to enlarge

If your flow loops through many items, Apply to each runs sequentially by default, which can be slow.

Turn on Concurrency control to process multiple items in parallel, but do it intentionally: too much parallelism can trigger API throttling and random failures.

Also be careful with variables when concurrency is on. Parallel iterations can update the same variable at the same time and produce inconsistent results. In these cases, prefer Compose actions inside the loop so each iteration keeps its own value.

A good pattern is to start small (for example, 2 to 5), monitor failures, and scale up only when the connector and backend can handle it.

Did this tip help you?

Vote once and classify what made this tip valuable.

Try this now

Quick checklist to apply this tip immediately.

Open your Apply to each action and enable Concurrency control.
Start with a low degree like 2 to 5, then test your run time and failures.
Avoid shared variables inside the loop; prefer Compose per iteration to keep values isolated.
Increase only if your target API and connectors can handle more parallel calls.

💬 Comments & Suggestions

Share your thoughts, tips, or drop a useful link below.

Enable JavaScript to view comments via Giscus.

Did this tip help you?

Try this now

Related tips

Configure Run After = try/catch for flows

💬 Comments & Suggestions