PA-010: Power Automate Foreach with very high concurrency
An Apply-to-Each (Foreach) action sets runtimeConfiguration.concurrency.repetitions above 50, which can overwhelm downstream APIs and hit connector throttling limits without the flow being aware.
What it detects
An Apply-to-Each (Foreach) action sets runtimeConfiguration.concurrency.repetitions above 50, which can overwhelm downstream APIs and hit connector throttling limits without the flow being aware. Flowcerta surfaces this finding from the active validation pipeline for supported file types and platforms.
Why it matters
Performance findings matter because small workflow anti-patterns multiply at production volume. Unbounded loops, unnecessary child workflow calls, and inefficient waits turn routine bot work into avoidable runtime cost.
Example violation
An Apply to each loop sets runtimeConfiguration.concurrency.repetitions to 75 against a downstream connector that throttles at 50 requests per minute, triggering 429s mid-run.
Fix guidance
Power Automate
- Lower the concurrency.repetitions setting to a value the downstream API can sustain, or remove the override to use Power Automate's default sequential iteration with bounded retries.
- Prefer environment-aware connectors, connection references, structured scopes, and explicit run-history logging.
- Revalidate the workflow after the change and confirm the finding no longer appears.
Verification steps
- Run validation again and confirm the rule no longer appears in the finding list.
- Review the changed workflow artifact directly to verify the risky pattern is gone.
- Capture the new validation result as evidence for the relevant owner or compliance review.
Compliance references
Related rules
This page is generated from the canonical Flowcerta rule registry used by validation scoring.
Browse all rule playbooks