Docs
FC-UIP-FLOW-001: Nested flowchart
Flowchart is nested inside another flowchart.
What it detects
Flowchart is nested inside another flowchart. Flowcerta surfaces this finding from the active validation pipeline for supported file types and platforms.
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 UiPath flowchart contains another flowchart inside one of its decision branches.
Fix guidance
UiPath
- Keep flowcharts as top-level orchestration layers and extract nested decision logic into a child workflow.
- 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 canonical Flowcerta rule registry used by validation scoring.
Browse all rule playbooks