You are here:
Define the Run Order of Record-Triggered Flows for an Object
Specify a trigger order value to determine the run order of before-save or after-save flows for the same object.
Required Editions
Declaratively configure a flow to run before or after another flow. Order your flows to help ensure consistent results without creating overly complex flows, letting you divide automation by teams or logical owners.
When you save a before- or after-save record-triggered flow, specify a trigger order value
from 1 to 2,000. If a flow is already saved, specify a trigger order value in the flow’s
version properties.
Guidelines for Defining the Run Order of Record-Triggered Flows for an Object
Learn guidelines for configuring a record-triggered flow to run before or after another record-triggered flow.
- You can define a trigger order value only for before-save or after-save flows on an object. Trigger order affects only the specified object's flows with the same trigger type.
- Trigger order values always respect order of execution rules. For example, you can make an after-save flow run before other after-save flows, but you can’t make an after-save flow run before a before-save flow or an Apex trigger, even if the trigger order value is lower.
- Flows with the same trigger (before- or after-save) on the same object with trigger order values from 1 to 1,000 run in ascending order (1, 2, 3, and so on). Multiple flows with the same trigger order value run in alphabetical order based on the flows’ API names.
- Flows without trigger order values run next and in the order of their activation dates. Flows created in Winter ’22 and earlier run in this order, unless you define a trigger order value for them.
- Flows with trigger order values from 1,001 to 2,000 run next and in ascending order. Multiple flows with the same trigger order value run in alphabetical order based on the flows’ API names.
- When you order a large number of flows, a best practice is to evenly distribute the trigger order values, for example, 10, 20, 30, or 100, 200, 300. Then later, you can easily slot another flow in between, for example, between 10 and 20. This practice can help you avoid changing the trigger order values for pre-existing flows.
- Activating, deactivating, or changing the order for one flow can cause the order for other flows to automatically update. Ordering record-triggered flows has no direct effect on any associated scheduled or asynchronous paths.
Did this article solve your issue?
Let us know so we can improve!
