Error handling for events, Apex jobs and APIs

What the exam expects

• Handle platform event publishing failures from Apex: inspect each Database.SaveResult, retry temporary errors, and use a publish callback for the final result.
• Choose between setResumeCheckpoint() and EventBus.RetryableException in an event trigger, and explain what happens when a trigger reaches the error state.
• Recover Pub/Sub API publish and subscribe streams after errors, size fetch requests with flow control, and route each error code to automatic retry or to an engineer.
• Attach recovery to Apex jobs: Transaction Finalizers for Queueable jobs, BatchApexErrorEvent for Batch Apex.
• Design API error handling: allOrNone=false partial success, retry strategy by failure type, and logging and rollback standards.

Key terms: publish callback (Apex class that receives the final, asynchronous publish result); resume checkpoint (replay ID after which a failed trigger restarts); error state (a trigger that exhausted its retries and stopped receiving events); flow control (a Pub/Sub client requests only as many events as it can process); Transaction Finalizer (a System.Finalizer that runs after a Queueable job ends); partial success (valid records commit while failed ones return errors).

Key facts

Check yourself