What it requires. Record-triggered flows must define entry criteria (trigger filters) that restrict execution to only the records and field changes that require processing. A flow with no entry criteria runs on every save of every record of that object type, regardless of relevance.
Why it matters. A record-triggered flow with no entry criteria executes on every insert, update, or delete of the triggering object. In an org with thousands of records, this means the flow runs on every record save across all users and all integrations, consuming CPU time and potentially SOQL queries on every transaction regardless of whether the flow's logic applies. This accumulates rapidly in high-volume orgs and compounds with other flows and triggers sharing the same 10,000ms CPU time limit per transaction.
How to fix it. Add entry criteria to the flow trigger that restrict execution to the specific field changes or record conditions that require the flow's logic. Use IsChanged() for field-change-driven flows. For flows that must run on all saves, document the reason in the flow description.
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.