Flow Record-Triggered Max Per Object
Why is this an issue?
Having multiple record-triggered flows on the same object with the same trigger event and trigger type can lead to:
Unpredictable execution order: Salesforce does not guarantee the order in which multiple flows execute
Conflicting logic: Multiple flows may attempt to update the same fields with different values
Debugging complexity: Tracing which flow caused a particular change becomes difficult
Performance impact: Each additional flow adds overhead to record operations
Salesforce recommends consolidating record-triggered flows when possible, especially when they target the same object, event, and trigger type.
Examples
Example of incorrect configuration:
Multiple flows on Account with the same trigger:
Account_Validation_Flow- Before Save, CreateAccount_Field_Update_Flow- Before Save, Create
Example of correct configuration:
A single consolidated flow:
Account_Before_Create_Flow- Before Save, Create (handles both validation and field updates)
How can I fix violations?
Identify all record-triggered flows on the affected object with the same event and trigger type
Review the logic in each flow to understand what they do
Consolidate the flows into a single flow with ordered elements
Use decision elements to organize the logic clearly
Deactivate and delete the redundant flows
When should I disable this rule?
You may want to dismiss this issue if:
The flows are managed by different teams and consolidation is not practical
The flows have clearly separated responsibilities with no overlap
You are using subflows to organize logic and the entry flows are intentionally separate
Resources