Salesforce Order of Execution

Salesforce is predictable — not random

"It was working just a moment ago." If you work with Salesforce, you probably recognize this thought. A validation suddenly fires even though the value seems correct. An automation doesn't do what you expect. Or an integration sends data that's just slightly off.

At moments like these, Salesforce feels unpredictable. As if the system randomly decides what it will and won't accept. But that's not the case. Salesforce always follows the same sequence — with every change, every new record, every update.

What do we mean by 'order of execution'?

When you change something in Salesforce — update a field, create a new record, or data comes in through an integration — Salesforce doesn't execute everything at once. The system works with a fixed plan: first this, then that, and only then something else.

That plan is called the order of execution. It determines which checks, corrections and follow-up actions are executed in which order. And that order always applies — whether you're manually filling in a field, or an automation is updating a thousand records at once.

Salesforce doesn't work in one go, but in sequential steps. Those steps determine what happens when — and that's exactly where the confusion often arises.

Think of a conveyor belt

Imagine a factory with a conveyor belt. A product comes in, passes through various stations, and eventually comes out finished. Each station has its own task: check, adjust, approve, package.

Salesforce works the same way. Data comes in, passes through a series of checkpoints, gets adjusted if needed, and only then is permanently saved. After saving, follow-up actions sometimes occur.

This conveyor belt metaphor helps understand why the sequence matters so much. Each station has its own place — and you can't just change the order.

The big steps — without technical details

The exact Salesforce sequence has dozens of steps. But for understanding, you don't need technical depth. It's about the big picture:

Why this sequence matters so much

This fixed sequence explains many situations that seem strange at first glance. A few examples in plain language:

The sequence is always technically correct — but functionally it can feel like something's wrong. That difference is important to recognize.

How this relates to flows

When you work with Salesforce, you often hear about 'flows' — the automations used to automate processes. What many people don't know is that flows can run at different moments:

Since Spring '22, you can configure the order of multiple flows of the same type (Before Save or After Save) with Flow Trigger Order (1-2000). This lets you determine which flow runs first. This doesn't change the best practice of having 1 master flow per trigger type.

This distinction isn't a preference or setting — it's part of the fixed sequence. Whoever builds a flow needs to know at what moment that flow runs. For you as a product owner or process owner, it's mainly important to know this distinction exists, so you can ask the right questions to your consultant or admin.

What your organization gains from this

You don't need to memorize the sequence. You also don't need to be able to build flows yourself. But knowing there's a fixed sequence — and understanding what that roughly means — provides immediate benefits:

Understanding is already a win. You don't need to be able to build it to understand it.

Understanding before solution

Many problems that surface in Salesforce aren't bugs. They're the result of assumptions about sequence that don't hold. A validation that comes too early. An automation that runs too late. An integration that sends data before the correction is applied.

Whoever recognizes the sequence can better analyze where a problem comes from. And whoever understands the sequence makes better choices — whether it's about a new process, an adjustment to existing automation, or the question of whether something is even possible.