# Order of execution and trigger order

*Platform Administrator II Study Guide · Process Automation · Last updated October 26, 2026 · https://www.certifyforce.com/study-guide/platform-administrator-ii/process-automation/order-of-execution-and-trigger-order*

The save order of execution from before-save flows to post-commit email, what each automation can see when it runs, how roll-ups pull parents into the same save, what a recursive save skips, and how trigger order values sequence record-triggered flows.

- Certification: Salesforce Platform Administrator II
- Exam section: Process Automation
- Study guide: https://www.certifyforce.com/study-guide/platform-administrator-ii

**Official exam objective:**

> Understand the implications of the order of execution when using automation tools.

## What the exam expects

- Place before-save flows, before triggers, validation, duplicate rules, after triggers, assignment, auto-response, workflow and escalation rules, after-save flows, entitlement rules, roll-ups, sharing, commit and post-commit work in order, and predict what each one sees.
- Explain why a later automation's value wins, why a rule misses a value set after save, and why email is lost when a save rolls back.
- Explain what a workflow field update and a recursive save re-run or skip, and how roll-ups put parent records through the save.
- Sequence record-triggered flows with trigger order values, and know what those values cannot change.

Key terms: **order of execution** (the fixed sequence of events Salesforce runs when a record is saved); **save procedure** (that sequence run for one record, including a parent updated by a roll-up); **recursive save** (a second save of the same record in the transaction); **trigger order** (a 1-2,000 value that sequences flows with the same trigger on one object); **post-commit logic** (work that starts only after commit, such as sending email).

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Before-save flows | Run immediately before Apex before triggers | [Before-Save Flows](https://help.salesforce.com/s/articleView?id=platform.flow_concepts_trigger_record.htm&type=5) |
| Duplicate rules | Run after custom validation, before the record is saved | [Order of Execution](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm) |
| Assignment rules | Run after after triggers and before after-save flows | [Order of Execution](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm) |
| Entitlement rules | Run after after-save flows | [Order of Execution](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm) |
| Workflow field update | Re-runs system validation, not custom validation; update triggers fire once more | [Order of Execution](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm) |
| Roll-up parent | Goes through its own save procedure in the same transaction | [Order of Execution](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm) |
| Recursive save | Skips steps 9 (assignment rules) through 17 (grandparent roll-up) | [Order of Execution](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm) |
| Email | Sent post-commit only | [Order of Execution](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm) |
| Trigger order range | 1-2,000; equal values run alphabetically by API name | [Run Order of Flows](https://help.salesforce.com/s/articleView?language=en_US&id=platform.flow_task_trigger_run_order.htm&type=5) |
| Multiple Apex triggers, same event | Order not guaranteed | [Order of Execution](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm) |

## Check yourself

- Why does a duplicate rule compare values that a before-save flow cleaned up?
- When do flows without a trigger order value run?
- Why can inserting one detail record run the parent record's update flow?
- Which steps does a recursive save skip?
- What does a roll-up mass recalculation not trigger?

## Sources

- [Triggers and Order of Execution](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm)
- [Define the Run Order of Record-Triggered Flows for an Object](https://help.salesforce.com/s/articleView?language=en_US&id=platform.flow_task_trigger_run_order.htm&type=5)
- [Before-Save Record-Triggered Flows](https://help.salesforce.com/s/articleView?id=platform.flow_concepts_trigger_record.htm&type=5)
- [Process Order for Salesforce Automation Rules and Apex Triggers — Key Reminders](https://help.salesforce.com/s/articleView?id=000385534&language=en_US&type=1)
- [Workflow Considerations](https://help.salesforce.com/s/articleView?id=sf.workflow_rules_considerations.htm&language=en_US)
- [Roll-Up Summary Field](https://help.salesforce.com/s/articleView?id=platform.fields_about_roll_up_summary_fields.htm&type=5)
- [Record-Triggered Automation (Decision Guide)](https://architect.salesforce.com/docs/architect/decision-guides/guide/record-triggered)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 11 linked practice questions, and unlimited timed mock exams are included with the Platform Administrator II pack (USD $19): https://www.certifyforce.com/practice-exams