sfhero
Join communityNewsletter
Learn Apex
Order of execution
On save, Salesforce runs a defined sequence: triggers, validation, automation flows — order matters for recursion and side effects.
Timeline

Start with the official Order of Execution diagram. This page is a teaching ladder — real orgs add Flows, Platform Events, and async steps.

Walk the pipeline (tap Next)

  1. 1.before triggers
  2. 2.validation rules
  3. 3.after triggers
  4. 4.assignment rules
  5. 5.workflow / process (legacy paths vary)
  6. 6.flows (record-triggered — depends on config)

Highlighted: before triggers

Mini quiz: sort first 3

Correct order: before triggers → validation → after triggers.

after triggers
before triggers
validation rules

Answer: drag the list above — “before” always runs before validation; validation before “after” triggers.

Why it matters in Apex
// If validation fails, after triggers don’t run.
// If a before trigger updates the field again, validation may re-run.
// Always read the current Salesforce release notes for order details.