FC-UIP-PERSIST-002: Persistence with non-serializable variable
Workflow uses persistence while declaring a variable type that is unlikely to serialize safely across a persisted boundary.
What it detects
Workflow uses persistence while declaring a variable type that is unlikely to serialize safely across a persisted boundary. 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
Workflow uses persistence while declaring a variable type that is unlikely to serialize safely across a persisted boundary.
Fix guidance
UiPath
- Replace runtime handles with serializable DTOs or move the variable into a scope that cannot cross a persistence activity.
- 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