Skip to main content

SF-0098 · Concept · Medium

In which order individual actions and types of actions are executed in workflow?

✓ Verified by Vikas Singhal · Last reviewed 5/17/2026 · Updated for Spring '26

Workflow actions don’t fire in the order you list them in Setup. Salesforce has a deterministic order for action types — knowing it explains why field updates can cascade into other rules and why email alerts read the post-update values.

Immediate vs time-dependent

First, the high-level split:

  • Immediate actions fire as part of the current save transaction
  • Time-dependent actions are queued and fire later (after the configured wait)

Within each bucket, action types execute in a specific order.

The action-type order (within a save)

  1. Field Updates — run first
  2. Tasks — created next
  3. Email Alerts — sent
  4. Outbound Messages — fired last

Why this order matters:

  • Field Updates run first so that subsequent actions see the updated values. An email alert that includes {!Opportunity.Status} will use whatever a field update set it to.
  • Field Updates can re-trigger workflow rules if you enabled re-evaluation on the field update (the “Re-evaluate Workflow Rules after Field Change” checkbox). This is how a single save can chain through multiple workflow rules.
  • Multiple workflow rules on the same object are not ordered — their action sets are pooled and the action-type order applies to the union.

Where workflow sits in the broader order of execution

Within the full save pipeline, workflow runs after before/after triggers and after validation:

1. Load record values from request
2. System validation
3. Before triggers
4. System + custom validation rules
5. Duplicate rules
6. Save record (not yet committed)
7. After triggers
8. Assignment rules
9. Auto-response rules
10. Workflow rules        <-- here
    a. If a field update fires, fire before/after triggers AGAIN on that update
11. Process Builder / Flow (after-save flows)
12. Escalation rules
13. Entitlement rules
14. Roll-up summary recalc
15. Parent record save cascade
16. Commit DML
17. Post-commit logic: emails, async Apex, etc.

This is from the official order-of-execution documentation — worth memorising for senior interviews.

Time-dependent actions

These are queued in the Time-Based Workflow Queue (Setup → Monitor). When their scheduled time arrives, the platform re-checks the rule criteria — if the record no longer meets them, the action is discarded instead of firing.

What interviewers want

  • The four-step order: Field Updates → Tasks → Email Alerts → Outbound Messages
  • The reason: field updates run first so downstream actions see updated values
  • Bonus: where workflow sits in the order of execution (after triggers, before flows/Process Builder)
  • What is the order in which Salesforce processes rules?
  • How can we view pending time-based workflow actions?

Verified against: Apex Developer Guide — Order of Execution. Last reviewed 2026-05-17 for Spring ‘26 release.