Become a member

05 · Recursion control

Your after-update updates the record, which fires your after-update. Breaking the loop without breaking legitimate re-entry.

Article 10m 1 min read Updated 20 Jul 2025
05 · Recursion control
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

Your after-update updates the record, which fires your after-update. Breaking the loop without breaking legitimate re-entry.

Why a plain flag is wrong

A static 'hasRun' Boolean blocks the second batch of a 400-record update too — that is legitimate re-entry, not recursion. Track processed record Ids in a static Set instead.

Better: stop causing it

Most recursion is an after trigger doing a before trigger's job. Assigning field values on the in-flight record in before-save costs no DML and cannot recurse.

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