Exception Handling

💬 In plain words: Let exceptions bubble up to one central place. Catch them there, and permanently write the error to a custom Log__c record via a Platform Event so the log survives a database rollback. An empty catch block is how errors vanish without a trace—and haunt you in production. 📌 Real-Life Example: The Silent Integration Failure Imagine an integration that fails silently for a week because someone wrote catch(Exception e){} . To fix this, catch the error once at the top level and publish an Error_Event__e carrying the message and record ID. A subscriber then inserts an Integration_Log__c . Now, even if the main transaction rolls back, the rollback can't erase the evidence.

In plain words: A Null Pointer Exception (NPE) happens when your code tries to open an empty box. If a variable or object points to null (nothing) and you attempt to read its fields, call its methods, or get its list items, Apex crashes because there is no data in memory to work with. In Salesforce development, the System.NullPointerException is one of the most frequent runtime runtime errors. Because Apex is strongly typed but initializes unassigned object references to null , any attempt to traverse unpopulated relationships, empty map lookups, or unassigned variables will throw an unhandled exception. Writing defensive, null-safe Apex keeps your applications stable and prevents unexpected transaction rollbacks.