Docs

FC-UIP-RETRY-001: Try/catch inside retry scope

TryCatch nested inside a RetryScope suppresses the failure that RetryScope would retry on.

higherror handlinguipath

What it detects

TryCatch nested inside a RetryScope suppresses the failure that RetryScope would retry on. 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 TryCatch is nested inside a RetryScope, swallowing the exception that should trigger the retry.

Fix guidance

UiPath

  • Remove the inner TryCatch or move it outside the RetryScope so retries actually trigger on failure.
  • 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

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