PA-003: Power Automate retries disabled on external call
An HTTP or connector action sets retryPolicy to "none", removing the platform's default resilience against transient failures.
What it detects
An HTTP or connector action sets retryPolicy to "none", removing the platform's default resilience against transient failures. 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 connector action sets inputs.retryPolicy.type to "none", silently turning off the default exponential retry that protects against transient connector failures.
Fix guidance
Power Automate
- Remove the retryPolicy override to keep the default exponential retry, or set an explicit fixed/exponential policy with a sensible count.
- 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