Error Console
An Error Console in Salesforce is not one screen with that exact name.
Definition
An Error Console in Salesforce is not one screen with that exact name. The phrase describes the family of diagnostic surfaces a developer or admin opens when something fails: the Developer Console Logs tab for Apex runtime errors, the browser developer tools console for client-side JavaScript, Setup then Email Logs for email delivery failures, and Setup then API Usage for integration limit errors. Each surface catches a different kind of failure, and knowing which one to open is most of the skill.
There is no single Error Console button to click. People search for the term because they hit an error and want the place that explains it. The right answer depends on the layer that broke. Server-side Apex errors land in debug logs, UI errors land in the browser console, and platform-limit errors land in their own Setup pages.
Which diagnostic surface catches which failure
The Developer Console Logs tab for Apex errors
For server-side Apex, the Developer Console Logs tab is the surface people mean most of the time. Open it from the quick-access menu (your avatar) then Developer Console, and switch to the Logs tab at the bottom. The tab automatically polls and lists debug logs that capture database events, Apex processing, workflow, callouts, and validation logic for the current user. Set a trace flag for yourself on the Debug Logs page in Setup first, otherwise no log is recorded. Reproduce the failing action, then double-click the new log entry to open the Log Inspector. Uncaught exceptions appear as EXCEPTION_THROWN events with a class name, line number, and the message Apex returned. The filter box (case-sensitive) lets you jump straight to EXCEPTION or to a method name. If a value looks cut off, choose File then Open Raw Log, because the raw view does not truncate strings to 512 characters. This is where most production Apex mysteries get solved, since the stack trace tells you the exact line and the order of events that led to it.
The browser console for Lightning and Visualforce
Client-side errors never reach a Salesforce debug log, so the browser developer tools console is their home. Press F12 (or right-click then Inspect) in Chrome, Edge, or Firefox and open the Console panel. JavaScript errors from Lightning Web Components, unhandled promise rejections, failed network requests, and Content Security Policy violations all print here with a file and line reference. A component that renders blank, a button that does nothing, or a wire adapter that never returns data usually shows a red error in this console while the server logs stay silent. The Network tab in the same developer tools sits right next to it and shows the actual Aura or Lightning Data Service requests, their payloads, and their HTTP status codes. When a page half-loads, checking both the Console and Network tabs together tells you whether the break was in your JavaScript or in the server response it depended on. Train newer developers to open this console reflexively, because UI bugs hide here and almost never appear in the Apex logs they tend to check first.
Email Logs for delivery failures
When an email never arrives, the place to look is Setup then Email Log Files. Salesforce lets you request a log covering emails sent in the last 30 days, delivered as a CSV. Each row records the sender, the recipient, the date and time, the delivery status, and any error code the mail server returned. The Mail Event column is the key field. A D means the message was delivered. A P means a permanent failure, where the mail bounced back to the sender immediately, often a bad address or a hard rejection. A T means a transient failure that the server may retry. For Email Alerts that silently do nothing, Email-to-Case messages that go missing, or flow Send Email actions that seem to fire but produce nothing, this log is the first stop. Because the logs are requested rather than always-on, ask for one right after the failure window so the relevant sends are still inside the 30-day range. Pair this with Setup then Deliverability and Org-Wide Email Limits to rule out a daily send cap or a deliverability access level set below All Email.
API Usage and limit pages for integrations
Integration failures often are not code bugs at all, they are limit errors. Setup then API Usage shows your org against the 24-hour API request limit, with peak usage and the trend over time. A connected app or middleware job that suddenly throws REQUEST_LIMIT_EXCEEDED is telling you the org ran out of API calls, and this page confirms it. Several related Setup pages act as their own small error consoles for platform constraints. Org-Wide Email Limits shows the daily Apex and alert email cap. The various governor limits surface inside the debug log itself as a cumulative resource section, so a transaction that hits too many SOQL queries or too much CPU time reports the exact counter it blew. When an automated process works in a sandbox but fails in production, comparing these usage pages between the two orgs frequently explains the difference, since production traffic pushes the same code past a ceiling the sandbox never reached.
The Apex Replay Debugger for stepwise inspection
Reading a raw debug log line by line is slow. The Apex Replay Debugger turns a saved log into a real debugging session inside Visual Studio Code, and it is free in every org for all unmanaged Apex. Install the Salesforce Extension Pack, set breakpoints or checkpoints in your Apex class, trigger, or test, then run the Launch Apex Replay Debugger command against the captured log file. From there you step through execution, watch variables change, and hover over a variable to see its current value at that moment, the same experience as a live debugger but replayed from the log. It works with classes, triggers, anonymous Apex, and test runs. For a complex error where the stack trace alone does not explain how a variable reached a bad state, this is far more effective than scrolling text. Set the Apex Code log level to FINER or FINEST when you plan to use checkpoints, though avoid FINEST right before a deployment because heavy logging can slow the deploy considerably.
Building a routing habit instead of guessing
The reason Error Console is a useful mental label is that it forces one question: which layer failed? A short routing rule turns minutes of guessing into seconds. An Email Alert that did not send points to Email Log Files. A trigger throwing an exception points to the Developer Console Logs tab or the Apex Replay Debugger. A Lightning Web Component that will not render points to the browser console. An integration returning a limit error points to API Usage. Write these mappings into a team runbook so the knowledge does not live only in one senior developer head. The most expensive bugs are the ones investigated in the wrong place, where someone reads Apex logs for an hour while the real failure is a Content Security Policy block sitting in the browser console the whole time. Proactive surfaces complement the reactive ones. Setup then Health Check flags risky security settings before they cause errors, and the Optimizer and performance tools highlight conditions likely to fail under load, so some issues get caught before any user files a ticket.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Error Console.
- Apex Replay Debugger (Salesforce Extensions for VS Code)Salesforce
- Email Log ReferenceSalesforce
Hands-on resources to go deeper on Error Console.
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. When an Apex trigger throws an uncaught runtime exception, which Error Console surface is the primary place to read the stack trace?
Q2. A Lightning Web Component throws a client-side JavaScript error that never appears in any server-side Error Console. Where does it surface?
Q3. Why does Salesforce have no single button labeled Error Console?
Discussion
Loading discussion…