Error Console
The Error Console in Salesforce is the umbrella concept for the diagnostic surfaces where errors appear during development and troubleshooting: the browser''s developer console for client-side JavaScript errors, the Developer Console''s Problems tab for Apex compile errors, the System Log for runtime exceptions, the Email Logs page for email delivery failures, and the API Usage page for integration errors.
Definition
The Error Console in Salesforce is the umbrella concept for the diagnostic surfaces where errors appear during development and troubleshooting: the browser''s developer console for client-side JavaScript errors, the Developer Console''s Problems tab for Apex compile errors, the System Log for runtime exceptions, the Email Logs page for email delivery failures, and the API Usage page for integration errors. There is no single Error Console button in Salesforce; the term describes a category of diagnostic views that developers, admins, and integration engineers consult when something fails.
The most common error consoles by use case: for Apex code, the Developer Console''s Logs tab (catching debug logs and runtime errors); for Lightning Web Components, the browser''s developer tools console (catching client-side errors); for integrations, the Setup, then API Usage page combined with the Apex Trigger logs; for emails, Setup, then Email Logs. Each surface focuses on a specific failure mode; together they cover the platform''s troubleshooting needs.
The error surfaces in Salesforce development
Developer Console''s Logs tab
The most-used error console for Apex developers. Click your avatar, then Developer Console, then the Logs tab at the bottom. Set a Trace Flag for your user, reproduce the failing transaction, double-click the resulting log entry. Errors appear as EXCEPTION_THROWN events with stack traces; uncaught exceptions surface near the top of the log.
Browser developer tools console
For Lightning Web Components and Visualforce pages, the browser''s developer tools console (F12 in most browsers) catches client-side errors. JavaScript errors from LWC components, promise rejections, network failures, and CSP violations all appear here. The browser console is essential for diagnosing UI bugs that do not surface in Salesforce''s server-side logs.
Developer Console''s Problems tab
Inside the Developer Console, the Problems tab shows compile errors for any Apex class or trigger you have open. Save an Apex class with a syntax error; the error appears in Problems with line and column. The Problems tab is the IDE-style compile-error view; it complements the Logs tab''s runtime-error view.
Setup, Email Logs
Email delivery failures surface in Setup, then Email Logs. Each outbound email is logged with status (Delivered, Failed, Pending) and any bounce or rejection reason. For Email Alerts, Email-to-Case, and Marketing Cloud sends, this is the first place to look when emails do not arrive. Logs retain for 30 days.
Setup, API Usage and Org-Wide Email Limits
For integration errors, Setup, then API Usage shows API call counts, peak usage, and any errors against the per-org limits. Setup, then Org-Wide Email Limits shows daily email send limits and current usage. When integrations or automated emails silently fail, these pages reveal whether you hit a platform constraint.
The Apex Replay Debugger and structured error inspection
For complex Apex errors, the Apex Replay Debugger in VS Code transforms a saved debug log into a stepwise debugging session. Set Checkpoints in your Apex code, capture a log with the Replay Debugger configured, and step through the transaction watching variables change. This is more powerful than reading raw debug logs and is the modern way to inspect Apex errors.
Lightning Platform Performance Tools and unsupervised errors
Setup, then Performance Analyzer and Setup, then Lightning Components Logs surface errors users encounter in the Lightning Experience. Apex unhandled exceptions during page renders, Lightning component lifecycle errors, page render timeouts. Many of these errors never surface to developers; the Performance Tools catch them so production issues do not stay invisible.
How to investigate an error in Salesforce
Troubleshooting a Salesforce error means picking the right error console based on where the error happened. Apex errors go to the Developer Console; UI errors go to the browser; integration errors go to Setup pages.
- Identify the layer where the error occurred
Apex code error? Developer Console. Lightning Web Component error? Browser console. Email failure? Email Logs. Integration failure? API Usage. The layer determines the right error console to open.
- Open the appropriate error console
For Apex: Developer Console, then Logs tab. For LWC: browser F12, then Console tab. For email: Setup, then Email Logs. For integration: Setup, then API Usage.
- Set up logging if needed
For Apex errors, set a Trace Flag for the affected user with appropriate Debug Levels. Reproduce the issue. The log appears in the Developer Console.
- Read the error
In the Developer Console: search for EXCEPTION_THROWN. In the browser: scroll to the latest error with a red icon. The error message usually identifies the failing code and the cause.
- Trace to root cause
The error message names the symptom. Trace backward through the log or stack trace to find the originating code. For Apex, the line in your code where the exception was thrown is usually the smoking gun.
- Fix, deploy, and confirm
Make the fix in your code. Deploy to the affected environment. Reproduce the original scenario to confirm the error is gone. Document the fix in your change log.
Primary Apex error surface. Shows runtime exceptions with stack traces.
Compile errors for Apex classes and triggers.
Client-side errors for LWC, Aura, and Visualforce pages.
Outbound email delivery failures.
Integration call counts and error rates.
- Different errors surface in different consoles. An LWC error that does not show in the Apex log does not mean the code is fine; check the browser console.
- Trace Flags expire automatically. Long debugging sessions need fresh flags or you stop capturing logs mid-session.
- Email Logs retain only 30 days. Older email failures cannot be diagnosed from logs alone.
- Browser console errors are user-specific. An error one user sees does not appear in another user''s browser; reproduce in the affected environment.
Trust & references
Straight from the source - Salesforce's reference material on Error Console.
- Developer ConsoleSalesforce Help
- Email LogsSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. Where do Lightning Web Component errors typically appear?
Q2. Where do Apex errors typically appear?
Q3. What's the most general-purpose Salesforce-side debugging tool?
Discussion
Loading discussion…