Become a member

01 · Order of execution, the map

Before triggers, validation, after triggers, assignment rules, flows, roll-ups — what actually runs when you press Save.

Article 15m 1 min read Updated 08 Jul 2025
01 · Order of execution, the map
Modules
Apex Triggers
  1. Module overview
  2. 01 · Order of execution, the map
  3. 02 · One trigger per object
  4. 03 · The handler pattern
  5. 04 · Bulkification: 200 records or bust
  6. 05 · Recursion control
Data Model Basics
  1. Module overview
  2. 01 · Standard objects vs custom objects
  3. 02 · Relationship types, decided with three questions
  4. 03 · Record types and when not to use them
  5. 04 · Schema Builder, the honest map
  6. 05 · Junction objects in practice
Integration Patterns
  1. Module overview
  2. 01 · Request-reply with named credentials
  3. 02 · Fire-and-forget with platform events
  4. 03 · Batch sync without tears
  5. 04 · Middleware or point-to-point?
  6. 05 · Watch: a callout built end to end

Before triggers, validation, after triggers, assignment rules, flows, roll-ups — what actually runs when you press Save.

Why the map matters

Half of all 'my field keeps getting overwritten' mysteries are two automations at different steps of the same save. You cannot debug what you cannot sequence.

The steps that bite

Before-save flows run before before-triggers. Workflow field updates re-fire triggers. Roll-ups run late. Print the diagram and pin it where you debug.

Practice in your org

  • Open your Developer Edition org and follow along step by step
  • Change one thing at a time and note what happens
  • When something breaks, read the error before searching for it