Docs

ANL-006: Delay Activity

Hard-coded Delay activity detected.

mediummaintainabilityuipath

What it detects

Hard-coded Delay activity detected. Flowcerta currently surfaces this finding from the active validation pipeline for supported patterns.

Why it matters

Maintainability findings matter because they amplify operational drag over time. Bots with deep nesting, arbitrary waits, or hidden assumptions are harder to review, fix, and safely change.

Example violation

A fixed Delay activity is used instead of a state-based wait or bounded retry pattern.

Fix guidance

UiPath

  • Replace with element-exist or retry scope wait pattern.
  • 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-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