FC-UIP-ARG-003: Undefined output argument
An Out or InOut argument is declared on the workflow but no activity in the body assigns a value to it. Callers will receive the type's default value.
What it detects
An Out or InOut argument is declared on the workflow but no activity in the body assigns a value to it. Callers will receive the type's default value. 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
An Out or InOut argument is declared on the workflow but no activity in the body assigns a value to it. Callers will receive the type's default value.
Fix guidance
UiPath
- Wire the argument to an Assign.To, an activity Result attribute, or a similar output binding so the workflow actually produces the documented output.
- 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