Salesforce Troubleshooting Guide for Errors in Custom Code (Apex, Visualforce, Aura Component, Lightning Web Components)

First, confirm and record the basic information about the error.

Basic Error Information

• Specific time the error occurred (e.g., 2025/06/10 17:00:00 - 17:00:30)
• Whether it occurs only in a specific organization
• Whether it occurs only for a specific user
• Whether it occurs only for a specific record
• Whether it's a newly created development or something that suddenly stopped working
• Whether an error message is displayed on the screen

If an error occurs in Apex

Refer to Related Document to obtain debug logs when the error occurs and check if there are any error messages in the debug logs.

If an error occurs in Visualforce

Check if an error message is displayed on the screen.

Refer to Related Document to obtain debug logs when the error occurs, confirm whether Apex classes and triggers are called, and check if these processes have errors.

Check if an error message is displayed in the "Console" tab of the browser developer tools when the error occurs.

If an error occurs in Aura Component and LWC

Refer to Related Document and enable debug mode for the user experiencing the error.

Check if an error message is displayed in the "Console" tab of the browser developer tools when the error occurs.

If the issue is not resolved after checking all the contents of the above guide, please provide the information for investigation in your environment and for reproduction in our verification environment according to the content of the article below.

Provide the following information to customer support

1. Basic Error Information (occurrence time, scope of occurrence, message content, etc.)

2. The username of the user for whom login access permission has been set, referring to Related Article.

3. Name of the target development.

4. Specific reproduction steps.

5. For Aura Component and LWC, please also provide the following information:

   1. Browser type and version used (e.g., Google Chrome Version 137.0.7151.57)

   2. Screenshot of the "Console" tab of the browser developer tools when the issue occurred.

   3. HAR file when the issue occurred.

   4. If a stack trace is displayed on the screen, attach the full error message as a text file to the case.

6. Other information investigated or confirmed by the customer, and methods for reproducing the issue in support organization