How to check the debug logs in salesforce


  1. Login as a System Administrator to and click on the Setup link.
  2. On the left side navigation under “Administration Setup”, expand the Monitoring section.
  3. Click on the “Debug Logs” option (shown below)

To view a debug log, from Setup, enter Debug Logs in the Quick Find box, then select Debug Logs. Then click View next to the debug log that you want to examine. Click Download to download the log as an XML file.


How to use debug logs in Salesforce to troubleshoot?

  • Processes created in the Process Builder appear as flows and workflow rules in debug logs. …
  • Record change processes appear as flows of type Workflow. …
  • Immediate actions that are executed in a block are strung together in the flow. …
  • Scheduled actions are executed after a FLOW_WAIT element. …

More items…

How to enable debug logs?

Log on to the computer as a member of the local administrators group. Launch Event Viewer. Select ViewShow Analytic and Debug Logs. Navigate to Event Viewer (Local)Applications and Service LogsMicrosoftUser Experience VirtualizationApp Agent. Right-click on Debug under App Agent and select Enable Log.

What are debug logs and how do I use them?

  • Each debug log must be 20 MB or smaller. …
  • System debug logs are retained for 24 hours. …
  • If you generate more than 1,000 MB of debug logs in a 15-minute window, your trace flags are disabled. …
  • When your org accumulates more than 1,000 MB of debug logs, we prevent users in the org from adding or editing trace flags. …

How do I collect debug logs?

To collect debug logs

  • Right-click on “Debug” node and select “Save all events as”.
  • Choose a location and a file name and Save.
  • Choose “Display information for these languages” and select “English (United States)”.
  • Click “Ok”.

How do I capture a debug log?

1:427:47Turning on Debug logs in Salesforce | SFDC Online Training – YouTubeYouTubeStart of suggested clipEnd of suggested clipAnd the triggers to view saved debug logs from setup enter debug logs in quick fine box and thenMoreAnd the triggers to view saved debug logs from setup enter debug logs in quick fine box and then select debug logs when users start to retain debugging logs user can view download. Or delete user logs

How do I debug in Salesforce?

Use the Log InspectorFrom Setup, select Your Name > Developer Console to open Developer Console.Select Debug > Change Log Levels.Click the Add/Change link in General Trace Setting for You.Select INFO as the debug level for all columns.Click Done.Click Done.Select Debug > Perspective Manager.More items…

What is a debug log?

Debug logs are system-generated logs that are sent to your Dashboard along with every new conversation. They only appear if your developers have configured them in the SDK for a given game/app version.

What is debug mode in Salesforce?

When you enable debug mode, framework JavaScript code isn’t minified and is easier to read and debug. Debug mode also adds more detailed output for some warnings and errors. As with production mode, custom component code is not optimized or minified. Important Debug mode has a significant performance impact.

What is debug level in Salesforce?

A debug level is a set of log levels for debug log categories, such as Database , Workflow , and Validation . A trace flag includes a debug level, a start time, an end time, and a log type. The log types are DEVELOPER_LOG , USER_DEBUG , and CLASS_TRACING .

How do I view integration logs in Salesforce?

You can find the Integration Log by going to Settings > Integration Log, but in most cases you’ll see an alert either in the System Messages Widget or on the Messages area of the main navigation, like this: Clicking on any of the links will bring you to a list of all the integration tasks with uncleared errors.

Why do I have a debug log file?

The debug. log file is the default log file that Chromium-based browsers use when logging an error that is encountered. While Google has not officially explained the bug, based on the error, Chrome is running into an issue iterating over the files and subdirectories in a folder and logging it as an error.

Debug Logs in Salesforce

Debug logs in Salesforce are the best source of information to uncover what is actually taking place on the platform. These are the best option to track back events that might have happened in the Org. Specifically, if we are doing root cause analysis for a particular problem, we can trace out the root cause from the debug logs.

Use cases of debug logs

Debug logs can be used by the developers for tracing any errors that might have occurred on the application. For example, the application is not stable or it is impacting the performance of the other components, or it might stop responding after a certain user input because exceptions are not defined.

Limitations of the Debug Log

Debug logs are undoubtedly helpful for monitoring the platform, but it has certain limitations as well.

Setting Up the debug logging

Debug logging can be activated for Apex classes & triggers and normal users. For this, trace flags need to be configured along with the debug levels, in the Developer Console. Each trace flag will contain the following:

Debug Log Details

Analyzing the debug log is an art, and might need prior experience as a developer or administrator. However, if you are aware of the components of the debug logs, at least you will be aware, where to look for what. The components of the debug log are mentioned below:

Debug Log Categories

Each debug level includes a debug log level for each of the following log categories. The amount of information logged for each category depends on the log level.

Debug Log Levels

Each debug level includes one of the following log levels for each log category. The levels are listed from lowest to highest. Specific events are logged based on the combination of category and levels. Most events start being logged at the INFO level.

Debug Event Types

The following is an example of what is written to the debug log. The event is USER_DEBUG. The format is timestamp | event identifier:


Leave a Comment