PA-008: Power Automate event trigger without conditions filter
A webhook or event-driven trigger has no `conditions` filter, so the flow runs on every event the connector emits — including ones the flow then immediately discards.
What it detects
A webhook or event-driven trigger has no `conditions` filter, so the flow runs on every event the connector emits — including ones the flow then immediately discards. Flowcerta surfaces this finding from the active validation pipeline for supported file types and platforms.
Why it matters
Performance findings matter because small workflow anti-patterns multiply at production volume. Unbounded loops, unnecessary child workflow calls, and inefficient waits turn routine bot work into avoidable runtime cost.
Example violation
A SharePoint "When an item is created or modified" trigger has no conditions filter, so the flow starts on every item change and pays the run cost even when it would immediately exit.
Fix guidance
Power Automate
- Add a `conditions` expression on the trigger so the flow only starts when the event is actually relevant. Server-side filtering is cheaper than running and exiting.
- Prefer environment-aware connectors, connection references, structured scopes, and explicit run-history logging.
- 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