Cert++
Close

Troubleshooting storefront errors on production versus non-production instances

Key Takeaway

On a production instance, debug logging is disabled. To troubleshoot an error there, capture the session ID, URL and exact time of the error, and use them to find the matching entry in the log files.

Troubleshooting a storefront error means finding the server-side cause behind what the shopper sees. Where you look depends on the instance. On non-production instances, the Request Log in the Storefront Toolkit shows errors and your custom log messages in real time. On production instances, you trace the error through the log files instead.

Production versus non-production

The two paths differ because of debug logging. The debug log level is always disabled on production instances. On non-production instances, debug is enabled for in memory logging. In memory logging powers the Request Log, but it doesn't create log files.

On any instance, start by writing down the actions that led up to the error. The next step depends on where the error happened.

If the error is on a non-production instance...

Use the Request Log to get more detailed error information.

If the error is on a production instance...

Note the session ID, URL and exact time of the error. Use them to find the matching error in the log files.

B2C Commerce Developer Study Guide

Checklist progress

0/237Learned

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other B2C Commerce Developer studiers. 796 members and growing.