Order of Execution and Governor Limits

Salesforce Platform FoundationsOrder of Execution and Governor LimitsWhat happens, step by step, when a record is saved, and the multi-tenant governor limits that every trigger, flow and API call must respect. Covers recursion, transaction boundaries, the Limits class, CPU-time pitfalls and how to monitor org-wide allocations.Intermediate · about 70 minutesWhat you will learn

Walk through the full save order of execution and place triggers, flows, validation, duplicate rules, roll-ups and sharing in it

Predict when the save procedure re-runs and prevent unwanted recursion

Explain why governor limits exist and recall the key synchronous and asynchronous per-transaction limits

Identify transaction boundaries for UI saves, API calls, Bulk API chunks, triggers and async jobs

Use the Limits and OrgLimits classes, the Limits REST resource and Setup pages to monitor consumption

Apply bulk patterns and avoid common Apex CPU time pitfalls

Contents

The save order of execution

Recursion and re-firing

Why governor limits exist

Per-transaction limits

Per-org limits and allocations

Transaction boundaries

Measuring limits in code: the Limits and OrgLimits classes

Bulk patterns for staying within limits

Apex CPU time pitfalls

Limits apply to flows, too

Monitoring limits

Worked example: diagnosing a data-load failure

Best practices

Common pitfalls

Hands-on exercises

Key takeaways