PA-007: Power Automate recurrence trigger fires too frequently
A Recurrence trigger is configured to fire more frequently than once every 5 minutes, which can burn API quota and is rarely necessary for business-event polling.
What it detects
A Recurrence trigger is configured to fire more frequently than once every 5 minutes, which can burn API quota and is rarely necessary for business-event polling. 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 Recurrence trigger is configured with frequency=Minute and interval=1, polling the source every minute and burning API quota when most events are routine.
Fix guidance
Power Automate
- Increase the interval to at least 5 minutes, or switch to an event-driven trigger (When an item is created/modified, webhook) so the flow reacts to real events instead of polling.
- 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