Docs

PA-001: Power Automate HTTP action without failure handler

HTTP or connector action has no downstream failure handler (runAfter: Failed/TimedOut).

higherror handlingpowerautomate

What it detects

HTTP or connector action has no downstream failure handler (runAfter: Failed/TimedOut). 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 Power Automate HTTP action posts to a downstream API but has no Compose or Scope action with runAfter set to Failed/TimedOut to catch the error path.

Fix guidance

Power Automate

  • Add a Scope action or a downstream step with runAfter configured to handle Failed and TimedOut outcomes.
  • 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

  1. Run validation again and confirm the rule no longer appears in the finding list.
  2. Review the changed workflow artifact directly to verify the risky pattern is gone.
  3. Capture the new validation result as evidence for the relevant owner or compliance review.

Compliance references

Related rules

FC-ANY-EXC-001FC-ANY-HTTP-001FC-ANY-RETRY-001

This page is generated from the canonical Flowcerta rule registry used by validation scoring.

Browse all rule playbooks