PA-004: Power Automate Do Until loop without a limit
A Do Until loop has no count or timeout limit, so a never-true exit condition runs until the platform's hard ceiling.
What it detects
A Do Until loop has no count or timeout limit, so a never-true exit condition runs until the platform's hard ceiling. Flowcerta surfaces this finding from the active validation pipeline for supported file types and platforms.
Why it matters
Error-handling findings matter because unattended automations fail in ways humans do not immediately see. Without bounded retries, exception capture, and logging, a single bad dependency can create silent data loss or prolonged instability.
Example violation
A Do Until loop checks a status field with no count or timeout limit declared, so a never-true exit condition runs until the Power Automate platform ceiling.
Fix guidance
Power Automate
- Set a limit with an explicit count and timeout that bound the loop to the expected iteration and duration range.
- 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