Missing condition on record-triggered flows
Why is this an issue?
Record-triggered flows execute every time a record is created or updated. Without entry conditions, the flow runs for every change, even when its logic is not relevant. This causes:
Unnecessary processing: CPU cycles wasted on records that don't need processing
Slower save operations: Users experience delays on every record save
Examples
Example of incorrect configuration: A flow that sends a notification when an opportunity is marked "Closed Won" but has no entry condition, so it runs on every opportunity update.
Example of correct configuration: The same flow with an entry condition: {!$Record.StageName} = 'Closed Won' AND {!$Record__Prior.StageName} != 'Closed Won'
This ensures the flow only runs when an opportunity is newly closed.
How can I fix violations?
Open the flow in Flow Builder.
Click Configure Start on the Start element.
Under Set Entry Conditions, select "Condition Requirements Are Met".
Define conditions that specify exactly when the flow should run.
Common patterns:
Field changed to a specific value:
{!$Record.Status} = 'Active' AND {!$Record__Prior.Status} != 'Active'Record meets criteria:
{!$Record.Type} = 'Enterprise'
When should I disable this rule?
You may dismiss specific violations for flows that need to run on every record change, such as audit logging flows.
Resources