What Is Order of Execution in Salesforce & Debug Log?

1
What Is Order of Execution in Salesforce Debug
Log?
2
INTRODUCTION

• Salesforce provides a bunch of rules that can be
  defined on objects and fields.
• As an example, you can define Validation rules,
  Workflow rules, Process Builder, Flows, etc.
• You need to understand the order of execution in
  which these rules and triggers are executed,
  whether you are an Administrator, Consultant,
  Developer, or Architect.

3
EVENTS TO SAVE A RECORD

• Salesforce conducts the following events in order
  when you save a record with an insert, update, or
  upsert statement.
• On the server, Salesforce
• Initializes the record for an upset statement by
  loading the original record from the database.
• Overwrites the old values with the new record
  field values loaded from the request.
• Runs record-triggered flows that are set to
  execute before the record is saved.
• Execute everything before the triggers.
• Verifies all necessary fields.

4
EVENTS TO SAVE A RECORD

1. Stores the record in the database, but does not
   yet commit it.
2. All after-triggers are executed.
3. Follows the rules of the assignment.
4. Enables auto-response rules to be executed.
5. Follows the workflow rules.

5
EVENTS TO SAVE A RECORD

• Updates the record once more.
• The system validations are re-run. Validation,
  flow, duplication, process, and escalation rules
  are not re-run.
• Regardless of the record operation (insert or
  update), executes one more time before and after
  update triggers (and only one more time).
• Check complete blog by Blueflame Labs, the
  salesforce implementation partners
• https//www.theblueflamelabs.com/order-of-executio
  n-in-salesforce/