Why does the Apply to each concurrency setting allow values up to 100 to be entered when the documented maximum is 50?

Question

Why does the Apply to each concurrency setting allow values up to 100 to be entered when the documented maximum is 50?

Kenjiro Suganuma（菅沼健二朗） 0

Hello,

I have a question regarding the Concurrency Control setting of the Apply to each action in Power Automate.

Based on the information I have found, my understanding is that the maximum supported concurrency value for an Apply to each loop is 50.

However, in the Power Automate designer, the Degree of Parallelism field allows me to enter values up to 100.

The confusing part is that values greater than 50 can be entered in the UI, but when I try to save the flow, the save operation fails and an error is returned. Values of 50 or lower can be saved successfully.

I would appreciate clarification on the following points:

Is the official maximum concurrency value for the Apply to each action still 50?
Why does the designer allow values up to 100 to be entered?
Is it expected behavior that values greater than 50 can be entered but cannot be saved?
Is this a known issue (for example, a UI validation issue), or is it an intentional design choice?
Is there any official Microsoft documentation that explains this behavior?

What I observed

Concurrency Control is enabled on an Apply to each action.
The Degree of Parallelism field accepts a value of 100.
When I attempt to save the flow with a value greater than 50 (for example, 100), the save operation fails with an error.
Values of 50 or lower can be saved successfully.

From a user perspective, the UI suggests that values up to 100 may be supported, but the flow cannot be saved with those values. This difference between what the UI allows and what the platform accepts is confusing.

Could you please clarify the intended behavior and the actual supported limit?

Thank you for your assistance.

0 comments

2 answers

Your answer

Answer 1

Hello,

As the forum’s AI recommended, use a Degree of Parallelism between 1 and 50 for Apply to each. Microsoft’s concurrency guidance confirms that the supported maximum is 50.

The Power Automate limits documentation lists a separate range of 1–100 for trigger concurrency, which controls how many flow runs can execute at once. That range does not apply to iterations within an Apply to each loop.

Based on your tests, the failure to save values above 50 is consistent with the documented limit. However, without the exact error message, I cannot confirm the specific cause of the save failure.

The documentation confirms the supported limits, but it does not explain why the Apply to each field allows you to enter 100. It also does not identify that behavior as an intentional design choice or a known UI issue. The trigger’s 100 limit alone does not explain the designer behavior.

For now, keep the loop setting within 1–50. If you would like Microsoft to investigate the UI behavior, report it to Microsoft Support with the exact save error, a screenshot of the field, and whether you are using the new or classic designer. Please mask personal or sensitive information in anything shared publicly.

Answer 2

Yes. The documented maximum concurrency for an Apply to each action in Power Automate is 1 to 50.

The relevant documentation states that Apply to each loops execute sequentially by default and that the maker can set the degree of concurrency, or parallelism, from 1 to 50.

By contrast, the 1 to 100 range in the limits documentation applies to trigger concurrency control, not to Apply to each. The trigger setting and the loop setting are different controls:

Trigger concurrency control: 1 to 100 when turned on
Apply to each concurrency: 1 to 50

Based on that, the behavior described is consistent with the platform enforcing the documented Apply to each limit of 50 at save time.

For the specific UI behavior:

If the Degree of Parallelism field in Apply to each allows entering values above 50
but the flow fails to save when the value is greater than 50

then that indicates the designer is allowing input that the backend validation does not accept.

The provided documentation does not include an official explanation for why the designer permits values up to 100 in that field, and it does not explicitly describe this as an intentional design choice or a known issue. What is supported by the documentation is only:

the official Apply to each maximum is 50
the official trigger concurrency maximum is 100
concurrency settings can differ depending on whether the setting is on a trigger or on an Apply to each action

So the supported conclusion is:

Yes, the official maximum for Apply to each concurrency is still 50.
The documentation does not explain why the designer allows values above 50.
The observed save failure for values greater than 50 is consistent with the documented platform limit for Apply to each.
No official documentation in the provided material identifies this specifically as a known issue or intentional UI design.
The official documentation that explains the actual supported limit is the Apply to each concurrency guidance, and the separate flow trigger concurrency limits page explains where the 100 value applies.

References: