Become a member

02 · One trigger per object

Two triggers on one object run in an order Salesforce refuses to promise. The fix is a rule, not a framework.

Article 10m 1 min read Updated 11 Jul 2025
02 · One trigger per object
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

Two triggers on one object run in an order Salesforce refuses to promise. The fix is a rule, not a framework.

The rule

One trigger per object, ever. It contains no logic — it delegates every event to a handler class. Order becomes explicit, bypass becomes possible, tests become sane.

Enforcing it

A naming convention (AccountTrigger, AccountTriggerHandler) plus a code review checklist is enough. Frameworks help at scale, but the rule is what saves you.

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