Docs

ANL-002: Fragile Selector

UI selector uses volatile runtime attributes.

highselector qualityuipath

What it detects

UI selector uses volatile runtime attributes. Flowcerta currently surfaces this finding from the active validation pipeline for supported patterns.

Why it matters

Selector-quality issues matter because brittle automations break on harmless UI changes. A workflow that depends on volatile attributes creates recurring production noise and avoidable support effort.

Example violation

A UI automation selector relies on volatile runtime attributes such as idx or dynamic class names.

Fix guidance

UiPath

  • Replace dynamic attributes with stable visual identifiers.
  • 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

    This page is generated from the current runtime rule mapping and is not yet backed by canonical database rule metadata.

    Browse all rule playbooks