error-handling

Handle DML errors in Apex by processing Database.SaveResult to aggregate failures and using Platform Event logging to capture critical errors. This approach standardizes error reporting across services and batch processes without swallowing exceptions or adding in-flight DML overhead.

The best way to structure Apex exception handling for bulk operations is to implement service-boundary try-catch blocks and aggregate Database.SaveResult errors. This standardizes failures across triggers and batch processes while translating them into user-friendly messages.

Yes, you can use Platform Event logging to track critical Apex exceptions without adding DML in-flight. This method persists errors asynchronously, preventing silent failures and avoiding governor limits during bulk operations or integration point processing.

Create custom exception classes for domain-specific Apex errors by extending the base Exception class and adding rich context. Centralize try-catch logic at service boundaries to translate these domain failures into consistent, user-friendly messages.

Use addError for trigger validation to report row-level failures directly to the user, while service-boundary try-catch handles broader Apex exception aggregation. Combining both ensures robust error reporting without swallowing critical failures across the execution context.

Apex batch jobs fail silently when exceptions are caught and swallowed without logging. Implement centralized service-boundary try-catch with Platform Event logging to persist these failures, ensuring critical DML errors and validation issues are captured and reported reliably.