Docs
ANL-005: Excessive Nesting
Workflow nesting depth exceeds recommended threshold.
What it detects
Workflow nesting depth exceeds recommended threshold. 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
Nested sequences and decisions keep growing until the workflow is difficult to review or reason about.
Fix guidance
UiPath
- Extract nested logic into invoked workflows.
- 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
- Run validation again and confirm the rule no longer appears in the finding list.
- Review the changed workflow artifact directly to verify the risky pattern is gone.
- Capture the new validation result as evidence for the relevant owner or compliance review.
Compliance references
Related rules
This page is generated from the current runtime rule mapping and is not yet backed by canonical database rule metadata.
Browse all rule playbooks