You are here:
How Entry Conditions Work in Record-Triggered Flows
Entry conditions control when record-triggered flows run. Use AND, OR, custom logic, or formula-based conditions in the Start element to run your flow only when the right records change.
Required Editions
| View supported editions. |
How Entry Conditions Work and Why They Matter
The Start element is central to every record-triggered flow. First select the object of the triggering record and then select to have the flow trigger when you create, update, or delete a record.
Next, set up the entry conditions. Entry conditions are important because they limit when your flow runs. Without conditions, a flow can run on every record change and hit limits or cause unwanted automation. With conditions, the flow runs only when the record meets your criteria, which improves performance and keeps automation focused on the right records.
In the Set Entry Conditions section of the Start element, select how to evaluate the conditions so the flow determines when they’re met: all conditions met (AND), any condition met (OR), custom logic is met, or a formula that evaluates to true. Review each option to understand its behavior.
All Conditions Are Met (AND)
To run the flow when all conditions are true, use the All Conditions Are Met (AND) option. In the Set Entry Conditions section in the Start element, for Condition Requirements, select All Conditions Are Met (AND).
The flow runs only when a record goes from failing at least one condition to meeting all of them. If a record meets all the conditions, and they are still met after the record is updated, the flow doesn’t run. Salesforce schedules scheduled paths only if the previous version of the record didn’t meet the requirements, and the updated record does meet the requirements.
For example, a record-triggered flow runs when a user creates an account or updates an
account to meet these conditions: Industry equals Agriculture AND
Billing State equals CA.
For new records, Salesforce treats the before state as not meeting any conditions, so a new record that meets all conditions always triggers the flow.
| Scenario | Result |
|---|---|
A new account where:
|
The flow triggers because the record meets both conditions. Salesforce schedules any scheduled paths. |
A new account where:
|
The flow doesn't trigger. The record meets only one condition. Salesforce doesn't schedule any scheduled paths. |
An existing account where:
Updates to:
|
The flow doesn't trigger. The record met the conditions before the user updated the record, and the record still meets the conditions. Saelsforce doesn't schedule any new scheduled paths, but already-scheduled paths stay scheduled. |
An existing account where:
Updates to Industry = Agriculture |
The flow triggers. The record didn't meet the conditions before the update, but now meets the conditions. Salesforce schedules ant scheduled paths. |
Any Condition Is Met (OR)
To run the flow when a record meets one or more conditions, use the Any Condition Is Met (OR) option. In the Set Entry Conditions section in the Start element, for Condition Requirements, select Any Condition Is Met (OR).
This option triggers the flow only when an update causes a record to transition from meeting none of the conditions to meeting at least one. If a record met at least one condition before the update, the flow doesn't run, even if the record meets more conditions later. Scheduled paths follow the same rule: they're only scheduled when the update creates this transition, but any already-scheduled paths remain scheduled. If an update causes the record to stop meeting all conditions, Salesforce cancels any already-scheduled paths.
For example, a record-triggered flow runs when a user creates or updates an account record
and it meets at least one of these conditions: Industry equals Agriculture
OR Billing State equals CA.
For new records, Salesforce treats the before state as not meeting any conditions, so a new record that meets at least one condition always triggers the flow.
| Scenario | Result |
|---|---|
A new account where:
|
The flow triggers because one condition is met. Salesforce schedules any scheduled paths. |
An existing account where:
Updates to Billing State = CA |
The flow doesn't trigger. The record met at least one condition before the user updated the record. Salesforce doesn't schedule any scheduled paths, but already-scheduled paths stay scheduled. |
An existing account where:
Updates to Industry = Agriculture |
The flow triggers. The record didn't meet any conditions before, but at least one is met after the record update. Salesforce schedules any scheduled paths. |
An existing account where:
Updates to Billing State = NJ |
The flow doesn't trigger. After the record update, the record doesn't meet any of the conditions. Because the record doesn’t meet the conditions anymore, Salesforce cancels any scheduled paths. |
Custom Condition Logic Is Met
When you want to combine conditions in a specific way that isn’t simply all (AND) or any (OR), use custom condition logic. In the Set Entry Conditions section in the Start element, for Condition Requirements, select Custom Condition Logic Is Met. Then, in Condition Logic, enter an expression that references your conditions by number, such as 1 AND (2 OR 3).
The flow runs only when the custom logic expression evaluates to true for the triggering record. The same rule applies as for AND and OR. The flow runs only when a user creates or updates the record to meet the condition requirements. Scheduled paths follow the same behavior as other condition types.
For example, a record-triggered flow runs when a user creates or updates an opportunity record and meets this condition logic 1 AND (2 OR 3).
- Condition 1: Stage | Equals | Proposal
- Condition 2: Amount | Is Changed | True
- Condition 3: Close Date | Is Changed | True
The flow runs only when an opportunity is in the Proposal stage and the user updates either the Amount field or the Close Date field.
| Scenario | Result |
|---|---|
New opportunity created with:
|
The flow triggers because the record meets the custom logic. Salesforce schedules any scheduled paths. |
Existing opportunity with:
Updates to Amount = 10000. |
The flow triggers. The record meets condition logic 1 AND (2 OR 3): Stage is Proposal and Amount Is Changed is true. Salesforce schedules any scheduled paths. |
Existing opportunity with:
Updates to Close Date = three months from now. |
The flow triggers. The record meets condition logic 1 AND (2 OR 3): Stage is Proposal and Close Date Is Changed is true. Salesforce schedules any scheduled paths. |
Existing opportunity with:
Updates to:
|
The flow doesn't trigger. The record meets condition 1, but doesn't meet condition 2 or 3 (Amount and Close Date weren't changed). Salesforce doesn't schedule any scheduled paths. |
Considerations for Formula Evaluates to True
When the best way to express your entry criteria is in a single formula, use Formula
Evaluates to True. In the Set Entry Conditions section in the Start element, for Condition
Requirements, select Formula Evaluates to True. Then enter a formula
in the Formula field that returns true or
false. The formula can reference fields on the triggering record and
formula functions.
The flow runs only when the formula evaluates to true for the triggering
record. For new or updated records, the flow runs only when the formula evaluates to true.
Salesforce schedules or cancels scheduled paths the same way as for other condition
types.
For example, a record-triggered flow runs when a user creates or updates an opportunity record to make this formula evaluate to true AND(Amount > 10000, TEXT(StageName) = "Proposal"). The flow runs only when the opportunity amount is greater than 10,000 and the stage is proposal.
| Scenario | Result |
|---|---|
New opportunity created with:
|
The flow triggers. The formula evaluates to true. Salesforce schedules any scheduled paths. |
Existing opportunity with:
Updates to Amount = 20000. |
The flow triggers. The formula was false before and is true after the update. Salesforce schedules any scheduled paths. |
Existing opportunity with:
Updates to Stage = Closed Won. |
The flow doesn't trigger. The formula evaluates to false after the update. Salesforce cancels any scheduled paths.. |
When to Run the Flow for Updated Records
If your flow is set to run when a record is created or updated or only updated, and you’re setting conditions, consider how often you want the flow to trigger on update. This option shows only after you specify entry conditions.
In the Start element, under Set Entry Conditions, for When to Run the Flow for Updated Records select one of the following.
- Every time a record is updated and meets the condition requirements — the flow runs on every update to the record, as long as the record meets your entry conditions after the update. It doesn’t matter whether the record already met the conditions before the update. Use this option when you want the flow to run on any change to a record that currently meets your criteria.
- Only when a record is updated to meet the condition requirements — the flow runs only when an update causes the record to meet your entry conditions. It didn’t meet them before, but now it does. If the record already met the conditions and still does after the update, the flow doesn’t run. Use this option when you want the flow to run only when a record transitions into meeting your criteria, which reduces unnecessary runs and is required for scheduling paths from the Start element.
