Docs

FC-UIP-LOG-002: WriteLine activity in production workflow

WriteLine activity left in the workflow.

lowobservabilityuipathUiPath ST-MRD-011

What it detects

WriteLine activity left in the workflow. Flowcerta surfaces this finding from the active validation pipeline for supported file types and platforms.

Why it matters

Observability findings matter because teams cannot govern what they cannot see. Sparse or inconsistent logging slows investigations and weakens audit evidence.

Example violation

WriteLine activity left in the workflow.

Fix guidance

UiPath

  • Replace WriteLine with structured LogMessage checkpoints appropriate for production monitoring.
  • 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

    FC-ANY-LOG-001

    This page is generated from the canonical Flowcerta rule registry used by validation scoring.

    Browse all rule playbooks