Docs

FC-ANY-HTTP-001: Missing try/catch around external call

HTTP or web service call is not wrapped in a Try/Catch block.

higherror handlinguipath

What it detects

HTTP or web service call is not wrapped in a Try/Catch block. 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

HTTP or web service call is not wrapped in a Try/Catch block.

Fix guidance

UiPath

  • Surround all external HTTP calls with Try/Catch and log or rethrow exceptions.
  • 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-RETRY-001FC-ANY-RETRY-002

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

Browse all rule playbooks