How would you prevent a Record-Triggered Flow from running unnecessarily?

Question

A Record-Triggered Flow updates related records whenever an Opportunity is modified, even when unrelated fields change. How would you optimize the Flow using entry conditions, decision elements, and execution settings to improve performance and avoid unnecessary updates?

#Trailhead Challenges #Flow

Venkat Yadav · Accepted Answer

Hi  @Durga Prasad Karnaty https://trailblazers.salesforce.com/profileView?u=005KX000004NmD1YAK  I would first check why the Flow is running on every Opportunity update. A few things I would suggest: Entry Conditions:  Run the Flow only when required conditions are met. Run Settings:  Use "Only when a record is updated to meet the condition requirements" where applicable. Check Field Changes:  Compare $Record and $Record__Prior to identify changes. Decision Element:  Continue only when relevant fields have changed. Avoid Unnecessary Updates:  Update related records only when needed. Best Practice:  Filter records early and avoid unnecessary DML operations to improve Flow performance. Hope this helps!

dhanush gunda · Answer

The accepted answer covers the basics. Here is a tighter pattern that avoids unnecessary runs.    1. Trigger setting: choose "Only when a record is updated to meet the condition requirements". With this setting the flow fires when the record changes from not matching to matching, not on every save.    2. Entry conditions: use "Formula Evaluates to True" for changed-field logic, for example ISCHANGED({!$Record.StageName}) || ISCHANGED({!$Record.Amount}) (or {!$Record.Amount} <> {!$Record__Prior.Amount}). If an unrelated field is edited, the flow never starts and uses no resources.    3. Use before-save for same-record updates. A fast field update on the Opportunity itself needs no extra DML and is far cheaper than an after-save flow.    4. Only touch related records that need it. Use Get Records with filters, then a Decision to skip empty collections. Build all changes in a collection variable and use a single Update Records element after the loop, never an Update inside a loop.    5. Add a guard against loops. If the flow updates records that can re-trigger it, add a condition so it only runs when the value actually differs from what you are about to write.        6. Verify: use Debug with a record where only an unrelated field changes and confirm the interview doesn't start, then watch the paused or failed interviews and run history after deployment.

How would you prevent a Record-Triggered Flow from running unnecessarily?

Trailhead Challenges

관련 학습

도움 더 받기