Docs

ERR-007: Infinite Retry No Limit

RetryScope or retry loop has no maximum retry count set

higherror handlinguipath • power_automate

What it detects

RetryScope or retry loop has no maximum retry count set Flowcerta currently surfaces this finding from the active validation pipeline for supported patterns.

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 retry loop runs without a finite retry limit, allowing the automation to spin indefinitely.

Fix guidance

UiPath

  • Set NumberOfRetries to a finite value (e.g. 3) and configure exponential backoff.
  • Use platform-native assets, credentials, bounded retries, and Log Message checkpoints instead of hardcoded literals or silent failure paths.
  • Revalidate the workflow after the change and confirm the finding no longer appears.

Power Automate

  • Set NumberOfRetries to a finite value (e.g. 3) and configure exponential backoff.
  • 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

    ANL-003ANL-004ERR-001

    This page is generated from canonical rule seed data plus the current runtime validation mapping.

    Browse all rule playbooks