Docs

ANL-003: Missing Retry Scope

Activity has no surrounding Retry Scope.

higherror handlinguipath

What it detects

Activity has no surrounding Retry Scope. 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 click, type, or external interaction runs without a Retry Scope around the unstable step.

Fix guidance

UiPath

  • Wrap unstable activities in a Retry Scope with 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.

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-004ERR-001ERR-005

    This page is generated from the current runtime rule mapping and is not yet backed by canonical database rule metadata.

    Browse all rule playbooks