Ordering multiple record-triggered flows on one object
Key Takeaway
Within one object and trigger type, flows with Trigger Order values 1 to 1,000 run first, flows with no value run next, and flows with values 1,001 to 2,000 run last.
When several record-triggered flows run on the same object, the Trigger Order value decides which one runs first. Admins set this number on each flow, or drag flows into order in Flow Trigger Explorer. Ordering gives consistent results. Ordering also lets you split automation into smaller flows owned by different teams, so you don't need one overly complex flow.
Setting a Trigger Order value
A Trigger Order value is a number from 1 to 2,000 that you give a before-save or after-save record-triggered flow. You set it when you save the flow, or in the flow's version properties if the flow is already saved.
A typical reason to order flows is that one flow must set a field before another flow uses it. Another typical reason is that the related records each flow creates must appear in a certain order.
When you order a large number of flows, a best practice is to space the values evenly, such as 10, 20, 30 or 100, 200, 300. You can then slot a new flow in between, for example at 15, without changing the values of existing flows.