Share Your Experience With Others

Order of Execution in Salesforce

On the Server of Salesforce

  • Loads the original record from the database or initializes the record for an upsert statement.
  • Loads the new record field values from the request and overwrites the old values.
  • System Validations
  • Custom Validations
  • Executes all before triggers.
  • Runs most system validation steps again, such as verifying that all required fields have a non-null value, and runs any user-defined validation rules.
    (when the request comes from a standard UI edit page) is the enforcement of layout-specific rules.Salesforce doesn’t run a second time
  • Executes duplicate rules.
    If the duplicate rule identifies the record as a duplicate and uses the block action,
    the record is not saved and no further steps,
    such as after triggers and workflow rules, are taken.
  • Saves the record to the database, but doesn’t commit yet.
  • Executes all after triggers.
  • Executes assignment rules.
  • Executes auto-response rules.
  • Executes workflow rules.
  • If there are workflow field updates, updates the record again.
  • If the record was updated with workflow field updates,
    fires before update triggers and after update triggers one more time (and only one more time),
    in addition to standard validations.
    Custom validation rules, duplicate rules, and escalation rules are not run again.
  • Executes processes and flows launched via processes and flow trigger workflow actions.
    When a process or flow executes a DML operation, the affected record goes through the save procedure.
  • Executes escalation rules.
  • Executes entitlement rules.
  • If the record contains a roll-up summary field or is part of a cross-object workflow,
    performs calculations and updates the roll-up summary field in the parent record.
    Parent record goes through save procedure.
  • If the parent record is updated, and a grandparent record contains a roll-up summary        field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the grandparent  record.
    Grandparent record goes through save procedure.
  • Executes Criteria Based Sharing evaluation.
  • Commits all DML operations to the database.
  • Executes post-commit logic, such as sending email.

Leave a comment