Take a Flow Path Only When Certain Record Changes are Made

Now you can filter out record updates that are unrelated to your flow’s use case and avoid reprocessing records that previously triggered the flow. A flow that’s triggered by a record update can take different paths if the record that triggered the flow was edited to meet certain criteria. When you configure a Decision outcome, you can now set that outcome to execute only when the triggering record is updated to meet the condition requirements.

Where: This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.

Why: This option gives your flows a powerful filtering feature similar to the ISCHANGED function found in Workflow Rules and Process Builder and the oldMap/newMap variables found in Apex. Build more of your automation directly in Flow Builder without requiring Process Builder or Apex to check the prior version of the data.

How: On a record-triggered flow, configure the Start element to trigger when the record is updated, or when it’s created or updated.

The Configure Trigger screen, highlighting trigger options A record is updated, and A record is created or updated

To configure a Decision element’s outcome to only run when the triggering record is updated to match certain conditions, select Only if the record that triggered the flow to run is updated to meet the condition requirements.
The New Decision screen, with the ability to execute an outcome only if the record that triggered the flow to run is updated to meet the condition requirements
Note

Note

This option checks if the triggering record didn't previously meet the criteria and if the $Record variable, not the triggering record, now meets the criteria. If your flow changes any of the $Record variable’s fields before it runs the configured Decision element, the Decision checks if the $Record’s new field values now meet the criteria.