Troubleshooting with the debugger and Storefront Toolkit
How to work an error from production log evidence to a sandbox debug session, pick the right Storefront Toolkit tool, isolate SFRA upgrade regressions, and read script timeouts, cache side effects and deprecation messages.
Use debugging best practices and techniques to troubleshoot scripts and controllers and verify outcomes.
~7 min read · 10 practice questions ·
What the exam expects
- Follow the documented troubleshooting order: production evidence (session ID, URL, time) into log files, then reproduce and debug on a non-production instance.
- Choose the Storefront Toolkit tool that answers a question about a page: templates and controllers, content, caching, search scoring, request logs or preview.
- Run the SFRA troubleshooting checks and isolate whether a defect comes from base code or customizations.
- Explain script timeouts per context, why they can't be caught, and how a debug session changes them.
- Recognise side effects that show up while verifying outcomes: shortened cache times after script exceptions and deprecation log entries.
Key terms: Script Debugger API (the REST API IDE debuggers use for breakpoints, variables and expressions); Storefront Toolkit (six storefront overlay tools opened from Business Manager); Request Log (the toolkit tool that shows log entries for recent server calls); code compatibility version (the API behaviour level a code version runs with); script timeout (a per-context limit that aborts a script with a non-catchable exception); deprecation log (the system log of deprecated API usage).
Key facts
- Detail
- Note session ID, URL and exact time; find the error in logs
- Detail
- Not available on a production instance
debug log level on production- Detail
- Always disabled
- Detail
- Six tools
- Detail
- Red uncached, green cached
- Detail
- Same host name for storefront and Business Manager
- Detail
- 5 minutes
- Detail
- Minimum timeout for all contexts becomes 30 minutes
isscript exception- Detail
- Page cache time limited to 5 minutes
status="off" usage- Detail
- Logged with code location in the deprecation log
Sources for this section (6)
- Troubleshootingdeveloper.salesforce.com (opens in a new tab)
- Scriptsdeveloper.salesforce.com (opens in a new tab)
- Log Filesdeveloper.salesforce.com (opens in a new tab)
- Storefront Toolkit Toolshelp.salesforce.com (opens in a new tab)
- Examine Server Calls Using the Request Loghelp.salesforce.com (opens in a new tab)
- iscache Elementdeveloper.salesforce.com (opens in a new tab)
- Which timeout applies to form field validation scripts?
- When should you add code instrumentation?
- Why can the Request Log show your own log lines while you debug a script?
- When does an empty deprecation log tell you something useful?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the B2C Commerce Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 28 lessons of the B2C Commerce Developer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (10 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both