When there are a lot of Workflows, Validation Rules, Apex Triggers and the like, it can be hard to troubleshoot problems and issues. Debug Logs provide a trace of these actions to help. Here are a few tips that were not obvious from the online help.
- The Debug Log settings are at Setup, Administration Setup, Monitoring, Debug Logs. See online help on the specific options.
- A single Debug Log shows all of the code execution that occurred from a single user action. For example, when a user hits save on record, a Debug Log shows a trace of all the Validation Rules that were evaluated, Triggers that were run, Workflow Rules and Actions that were run, etc. The trace also shows several details of the code execution such as the Evaluation Criteria that were checked.
- Multiple Debug Logs will needed to be reviewed to track multiple user actions.
- Debug Logging occurs after you request a log. You cannot go back in time after a user has reported a problem. Issues need to be repeatable for Debug Logs to be useful.
- Be prepared to plow through a lot of data. It really is a dump of information. Filtering is available if you really know what you are looking for.
- Use your browser’s Find feature to search for Workflow names and the like.
- If you are troubleshooting Sites, it is possible to get Debug Logs of the Site Guest User. Enter “Site Guest User, <>”. Substitute the name of the Site for <>. The User picklist does not work, but entering this directly does work.