Search and filter the unique events of your sandbox logs, read each one with its resolved stack trace, and jump to the code that logged it
The Events tab of Log Center turns tailed and parsed log entries into Unique events. Repeated messages collapse into one row with a count, so a noisy log becomes a short list you can rank, filter, and open. Each event links back to the log files it came from and to the source line that logged it
147// A disabled payment method resolves to null here.
SFCC Logs: 3 occurrences | Export SFCC log issue
148 var processorId = paymentMethod.paymentProcessor.ID;
149
150returnTransaction.wrap(function(){
151OrderMgr.placeOrder(order);
152returnprocessorId;
153});
154}
main
Narrow the grouped events by severity, open a group to read its resolved stack trace, then follow a source frame into the workspace file at the reported line
Type in Search events, stack traces, source paths, request ids..., or press / to focus it. Suggestions offer the plain text search first, then matching messages, sources, stack frames, request ids, session ids, and controllers or hooks. Use ↓↑ to move, Enter to apply, and Esc to close. Find in Logs in the Command Palette focuses the field too
The filter panel groups its controls. The Filters head shows how many are active, and Clear all removes them. Each active filter also shows as a chip, such as Level: ERROR or Time: Last hour
Search suggestions, the HTTP status picker, the context and trace pickers and a drag on the histogram each add an Active chip, and every filter narrows the events table and the Messages over time chart
Group
Filters
Event
File type, category, level (All levels, ERROR, WARN, INFO, DEBUG, Other, with counts), HTTP status, the parsed Log files, and the time range from Last 15 min to Last 14 days, or a Custom range
Context
Sites, Endpoints, Sessions, Source files, plus Source path and Request id text fields
Trace
Stack status (With stack, Direct, Resolved, Unresolved, No stack) and Source mapping (Mapped source, Script mapped, Unmapped)
Workflow
Include fixed, Backlog, Anomalies, Copy fix prompt, and Investigate with MCP. See Triage and Fix
The HTTP status picker offers 4xx, 5xx, single codes such as 404 or 503, or No extracted status, and you can type a code to find it. HTTP context narrows by role (Inbound response, Outbound service) and service. Codes combine with OR, other filters with AND, and the Filters head sums up the matching codes, such as 502: 23 · 503: 13
Large menus load the most frequent values first. When a value is not listed, paste its exact text into the menu search to filter by it. Filters are saved per connection
HTTP status comes from entries parsed with the current parser. If older entries show under No extracted status, parse their files again with Read from beginning
The histogram charts the events that match the current filters:
The range pills switch between All, 15m, 30m, 1h, 2d, 5d, 7d, and 14d
Drag across the chart to zoom into a time window. The chart re-buckets to that window and a Time chip shows the range. Move its Range start and Range end handles to adjust it, and Reset returns to the full range
Click a row to open its drawer beside the table. The header shows the level, the occurrence count, the stack status, and when it last occurred. Search all sections with Search message, stack, endpoint, file, request…
WARN42m agoProduct demo-product has no price in the site price booksproductHelpers.js:212resolved1
WARN21h agoBasket total recalculated twice in one requestcartHelpers.js:96none1
main
Open an event group to see the code it resolves to, how often and where it happened, its stack trace and raw entry; For chat copies the full issue as Markdown for an AI chat or a ticket
Section
Shows
Resolved code
The controller route, hook, or script the event maps to, with Open path:line in editor
Occurrence summary
Occurrences, sites, sessions, and files, the observed window from first to latest seen, and the top sites and endpoints
Stack trace
Each stack, with the resolved frames linked to your files. Linked code only hides the others, and Show all N frames expands a long stack
Raw entry
The original log line
Log files and Source log file
Where the event was read from
Header, System, Request, Params
The fields SFCC wrote with the entry
Parsed JSON
The whole parsed entry in a read-only editor
Occurrence timestamps
Every time the event occurred
The toolbar has Expand all and Collapse all, Copy message, Message + stack, For chat (the full issue as Markdown for a chat or ticket), and Export for the selected event. Copied text is redacted: tokens, secrets, cookies, and authorization headers become <redacted>
Drag the drawer edge to resize it. Double-click the edge to reset its width
Stack frames and Resolved code open your local file at the logged line. Keep the workspace on the same code as the sandbox, so the lines match. For TypeScript, see Debug TypeScript on a Sandbox
storefront
placeOrder.js
app_customcartridgescriptscheckoutplaceOrder.js
141// Places the order once the payment method resolves.
📈 Unique events1📊 Total occurrences3🗂️ Log files2🌐 B2C instancezzrx-001.dx.commercecloud.salesforce.com🎯 ScopeSelected record group
Event #1 · 🔴 ERROR
⭕ MessageTypeError: Cannot read property "paymentProcessor" from null
mainLn 148, Col 1UTF-8SFCC JavaScript
Lines that analyzed logs point at show how often they failed. Open the event group in Log Center, or export it as a Markdown report
When a logged error maps to a source line, that line gets two Code Lenses. SFCC Logs: N occurrences opens the event in Log Center, and adds the file count when the occurrences come from several log files. Export SFCC log issue writes a Markdown report of the issue and opens its preview. See Code Lens
