The debug log contains information about each transaction, such as whether it was successful and how long it took. Depending on the filters set by your trace flags, the log can contain varying levels of detail about the transaction.
Required Editions
| User Permissions Needed | |
|---|---|
| To view, retain, and delete debug logs: | View All Data |
- To view a debug log, from Setup, use the Quick Find box to find and select Debug Logs.
- Click View next to the debug log that you want to examine.
- Click Download to download the debug log as a log file.
Debug logs have the following limits.
- Each debug log must be 20 MB or smaller. Debug logs that are larger than 20 MB
are reduced in size by removing older log lines, such as log lines for earlier
System.debugstatements. The log lines can be removed from any location, not just the start of the debug log. - System debug logs are retained for 24 hours. Monitoring debug logs are retained for seven days.
- If you generate more than 1,000 MB of debug logs in a 15-minute window, your
trace flags are disabled. We send an email to the users who last modified the
trace flags, informing them that they can re-enable the trace flag in 15
minutes.
Warning If the debug log trace flag is enabled on a frequently accessed Apex class or for a user executing requests often, the request can result in failure, regardless of the time window and the size of the debug logs. - When your org accumulates more than 1,000 MB of debug logs, we prevent users in the org from adding or editing trace flags. To add or edit trace flags so that you can generate more logs after you reach the limit, delete some debug logs.