Issues shows one row per repeated error or warning of the instance. Info and debug entries stay on Events. Select a row to read it in the details, a sidebar the full height of the view
Sandbox 01
version2
Files
Issues
Events
Anomalies
Monitor
Storage
Filters
Warn
Open Source
Mark Fixed
Move to Backlog
RefArch (3)
~/Projects/storefront
| The list reads | Because |
|---|---|
| No issues yet. Parse or tail a file on the Files tab. | Nothing is parsed for the instance yet. Events reads No events yet the same way |
| No issues match | The search or filters leave out every issue. Click Clear all filters. Events reads No events match with the same link |
| Issues lists only errors and warnings, and the level filter leaves out both | The Level filter keeps only info or debug. Click Clear the level filter |
| Loading… | The list is being read from the store |
| Could not load: … | The store could not be read, with the reason |
The list
| Column | Shows |
|---|---|
| Level | The level's icon and name |
| Issue | The issue's title, the rest of its first line in grey |
| Count | Its events. While filters narrow the issue, the events that match |
| Trend | Its events over the last 24 hours, in its level's colour |
| Last seen | How long ago it last logged, such as 12s ago, 5 min ago, 3 h ago or 2 d ago |
| Files | How many log files it was logged in |
| Source | The script line it points to, with the file's icon and the cartridge on the right. Its tooltip gives the path and line, and adds (No file of this project matches it) when the path is red |
- Select several issues with
ShiftorCmd/Ctrl.Cmd+C/Ctrl+Cor Copy in the menu copies one line per issue, its level, count, title and source, with secrets masked - Drag a column's edge to resize it. The widths are remembered
- The tab counts the issues, such as Issues 8. Large counts are shortened, such as 27K, and a + means at least that many while a search still counts
- Under 760 pixels wide, the details go under the list instead of beside it
The details
The details of an issue or an event start with its title on a wash of its level's colour: the error type when the message names one, such as TypeError, else the start of the message. Its tooltip gives the whole first line. On an issue, First seen and Last seen follow, each with how long ago, then Events with the count. Click a time to narrow the views to that minute, or the count to show the events. While filters narrow the issue, the count reads 37 matching of 1,204. With no row selected, the details read Select a row to see its details, and while they load, Loading...
Previous Issue and Next Issue, or Previous Event and Next Event, at the top move to the row before or after, without leaving the details. The IDE's Previous Occurrence and Next Occurrence keys do the same anywhere in the details, also while they are maximized. The tab you chose, such as Stack, stays chosen as you move between rows
| Action | What it does |
|---|---|
| Show Events | Shows the issue's events on Events. On an event, it shows when the event belongs to an issue |
| Open Source | Opens the script line from the stack trace in the editor. Shown when the issue has a source |
| Mark Fixed, Move to Backlog | See Mark fixed and keep a backlog. On issues only |
| Copy | Copy Message, Copy Stack, Copy Entry on an event, and Copy as Markdown for a ticket or an AI chat. An issue's Markdown adds its top 8 sites, sessions and log files and its latest 25 events. Secrets are masked |
| Investigate with MCP | Copies a prompt for an AI agent, see Fix with an AI agent. On issues only |
The summary under them shows the message, Where it was logged, the stack and the facts. Hide Summary folds it and Show Summary brings it back, and the choice is remembered. Drag the line above the tabs to resize it, or double-click the line to fit the summary to its content
- A long message shows its first 4 lines with Show more and Show less. A message that lists fields, such as
basketId=… customerNo=…, shows them as a grid of names and values: the first 8, then Show all 14 and Show less. A long value shows whole in its tooltip - Where shows the file's icon, the path and line as a link, the function in grey and the cartridge on the right. The path is red when no project file matches it
- Under it, Called from when Where is the stack's top frame, else Stack, lists the first 5 script frames, then Show all 12 and Show less. The stack counts its frames, such as 12 script frames, 3 in this project
- Without a Where line, the facts show the Top frame of the stack
- An issue's facts are its Level, Files and Category
- Right-click a value for Copy Value, which copies it whole
Rest the pointer on a value for its card:
- A script line: In the log with the path as logged, In this project with the file it opens, Cartridge and Function, then Open at line 9, or Open without a line, Show events from this source and Copy path. When no file matches, In this project reads No file of this project matches it in red. When several match, the card says 3 files match; opening asks which
- A value, such as a site: Show only events with … and Copy, plus Open route in code on a controller and Show request log on a session
- A time: the time, the time in UTC and how long ago, Show events around it, Show only this minute and Copy
- A log file: its Type, Size, Events, Modified and place On disk, Open log at line 4, Show only this file and Copy. A server log not downloaded yet reads Not downloaded yet: download it to open it here
The Source column of Issues and Events shows a path no project file matches in red. Opening such a source shows Not in this project: …, see Log sources in your project
Lay out the details
| Control | What it does |
|---|---|
| Hide Details | Gives the list the whole width and leaves a Details strip at the right. Click the strip, press Enter or Space on it, or double-click a row, to bring them back. Issues and Events each remember whether their details show |
| Maximize Details | Gives the details the whole view. Restore Details, or a double-click on a details tab, brings the list back |
| Full-Height Details | Switches between the full-height sidebar and details beside the list under the query bar, as Show details as a full-height sidebar in Settings |
Read an issue
Occurrences charts the issue's events over time. Drag across the chart to set that time range and show the issue's events on Events
Under the chart, bars show where the events come from, two lists to a row: Log files, Sites, Endpoints, and Sessions: 14, recurring: 3, which counts the sessions and those seen more than once. One session again and again is a user stuck, many sessions once a broken page. A long list shows its first bars with Show all 12 and Show less. Click a bar to filter by it and show the issue's events on Events
| Tab | Shows |
|---|---|
| Latest entry | The newest event as the log wrote it |
| Events | The events, newest first, with the count on the tab. Each row shows the level, time, file and line, site and endpoint. 25 a page with Previous and Next and a line such as Page 2 of 9, events 26 to 50 of 214. Enter or a double-click opens one in Events. If the page can't be read, it reads Could not load the events |
| Log | The newest 200 events as one log text |
| Stack | The stack trace, titled Stack trace, its first 24 frames. A longer stack reads 24 of 40 frames with Show all. Shown when the issue has a stack |
| Code | The project code the issue names: each place with its file, line, route or hook, a snippet and the cartridge. Enter or a double-click opens it. It reads Looking for the code this issue names..., then the code or No project code found for this issue |
Enteron an issue shows its events, andJandKmove through the rows- The Issue column strikes through issues marked fixed and adds backlog to issues in the backlog
Right-click an issue for Log Center: Open Row, Log Center: Open Row Source, Investigate with MCP, Mark Fixed or Mark Not Fixed, Move to Backlog or Remove from Backlog, and Copy
Read an event
Select an event on Events to see its facts: Time, Level, Site, Controller, Session, File with the line, Blade, HTTP status, Category and Thread
- Click a value to show only the events with it, such as one site, blade or HTTP status. Thread is plain text
- Click the time to open Around
- Click the file to open the log at the event's line, when it's a local or downloaded file. Otherwise the click shows only that file's events
| Tab | Shows |
|---|---|
| Entry | The entry as the log wrote it |
| Around | The 25 entries written before and after it |
| Request | Up to 2,000 entries of the same session, titled Request and the session. Shown when the event has one |
| Log | The newest 200 events of the event's issue, scrolled to this event and highlighting it. Shown when the event belongs to an issue |
| Selection (3) | Up to 5,000 selected events as one text, titled Selection of 3 events. Shown when you select more than one |
| JSON | The JSON the entry holds, formatted. Shown when the entry holds JSON |
Right-click an event for Show Selection in Log Viewer, which shows the selected events as one text, Log Center: Open Row Source and Copy. Copy and Cmd+C/Ctrl+C copy one line per event: its time, level, file and first line. In Unique, a row is a kind of event, and the right-click menu is the one of Issues
The text tabs, Latest entry, Log, Stack, Entry, Around, Request and Selection, show their text in the log viewer, with the colours, folds and clickable paths of a log open in the editor, see Logs in the Editor. A tab with more events than it holds says 200 events shown, the rest are left out, and text the store no longer holds reads The store no longer holds this text
Mark fixed and keep a backlog
Mark an issue fixed once you ship its fix, and move issues you will look at later to the backlog
| Action | What it does |
|---|---|
| Mark Fixed | Strikes the issue through and closes its details. Hide fixed in the Triage pill hides it |
| Mark Not Fixed | Opens it again |
| Move to Backlog | Adds backlog to the issue. Backlog hidden in the Triage pill hides it, Backlog only shows only the backlog |
| Remove from Backlog | Takes it out of the backlog |
If a fixed issue logs again after the fix, Anomalies reports it as a Regression. The row menu of Issues has Mark Fixed and Move to Backlog too, and you can give both keys in Settings › Keymap
Anomalies
Anomalies compares a recent window with the period before it and lists the issues that changed, most severe first. Incidents come first
Pick the window in Detection window:
| Window | Compared with |
|---|---|
| Last hour | The previous 7 hours |
| Last 24 hours | The previous 7 days |
| Last 7 days | The earlier parsed history |
| Selected range | The period 7 times longer before the time range in your filters |
| Type | Means |
|---|---|
| Regression | Marked fixed, but events kept arriving after the fix |
| New error | Never seen before this window in the parsed history |
| Spike | Far above its usual hourly rate |
| Returned | Seen long ago, silent through the comparison period, now back |
| Burst | Most events packed into a short stretch of the window |
| Spreading | Now hitting sites or endpoints it never hit before |
| Stopped | Used to occur steadily and went silent while the instance kept logging |
| Incident | A stretch where the whole instance logged far more than usual |
The view has the search, the pills and Filters of the other views, without a time range list: Detection window sets the time. Detect Again runs the detection on the parsed logs again
Beside the window, a line sums up the result, such as 3 anomalies in the last 24 hours · 1 critical · 2 high. Under the list, a line says what was compared: the window, 12,408 events in 316 patterns, and compared with 7 days of earlier logs. The tab counts the incidents and anomalies, and counts while the view shows
Read an anomaly
| Column | Shows |
|---|---|
| Type | The kind of anomaly. Its tooltip says what it means |
| Severity | Critical in red, High in the warning colour, Medium in the info colour or Low in the debug colour. Errors, HTTP 5xx and large changes rank higher. A Stopped pattern reads Resolved? in green and isn't counted in the summary |
| Anomaly | The level icon and the message, then a short headline in grey and, when one came near, the code change |
| Now vs usual | The events in the window against what the comparison period expects, such as 42 vs ~3, or 42, none before |
| Trend | The comparison period in grey beside the window in its severity's colour. On an incident, the whole timeline in grey with the incident's stretch in the error colour |
| Type | The headline reads, for example |
|---|---|
| Regression | 14 events after it was marked fixed |
| New error | New · 32 events since 2026-10-29 13:05 |
| Spike | 420 events vs ~131 expected (3.2×) |
| Returned | Back after 9 days quiet |
| Burst | 85% of events in 12 min |
| Spreading | Spread to 4 new site/endpoint contexts |
| Stopped | Stopped · ~40 expected, 0 seen |
Rest the pointer on a row for the whole story: one sentence per signal, such as Usual rate 3/h over 7 days of history; now 42/h, the code change, then Sites, Endpoints, New contexts, HTTP 5xx, Also for the other signals it matched, and Source
- Messages that differ only in URLs, emails, UUIDs or ids count as one pattern, so a known error on a new URL isn't new. Such a row adds · 4 variants to its headline, and its tooltip says 4 issues share this pattern (URLs, ids or numbers differ)
- When a code change, such as a deploy or a code version activation, came just before an anomaly began, or just after it stopped, the row names it in the colour of the timeline's marks, such as Code deployed to version2 from this IDE, 12 min before, …, as it began or …, 5 min after the last event. The tooltip adds A code change came just before and may have caused it, or came just after and may have ended it
- An Incident row reads Incident 2026-10-29 13:20 to 13:45 · 4,210 events, 6.2× the usual volume, then Led by and the issues that logged the most in it
- Click a row to select its issue for Export and the triage actions. Double-click it or press
Enterto show its issue's events on Events.Cmd+Enter/Ctrl+EnterorF4opens its source,JandKmove through the rows,/andCmd+F/Ctrl+Fgo to the search - The list keeps its order, most severe first: it has no sorting and no right-click menu. The selected row stays selected when the detection runs again
- The detection also runs when your filters change, and when new events arrive, at most every 5 seconds while the view shows. A result that went stale while the view was hidden runs again when it shows
- An Incident row's Type has a warning icon
When the list is empty or limited
| The view reads | Means |
|---|---|
| Detecting anomalies… | The detection runs |
| Could not load: … | The store could not be read, with the reason |
| Nothing unusual | No new errors, spikes, bursts, regressions or new sites and endpoints compared with earlier logs |
| No parsed events match the current filters in this window | Pick a longer window or parse more log files |
| No time range is set in the Log Center filters, so the last 24 hours are analyzed | Selected range with no time range in the filters |
| No events were parsed recently, so the window ends at the newest parsed event | Nothing new arrived. Start tailing or parse newer files to analyze current activity |
| Only 2 days of earlier history is parsed; rates are compared per observed hour | The comparison period isn't full |
| Only 3 h of parsed history exists before this window, so new, spike, spread and stopped signals are off | Parse older log files or pick a shorter window |
Errors in the editor
Script and ISML lines named by the open issues of the project's instance get a mark in the editor gutter, the error or warning icon of the line's worst issue. Fixed issues aren't marked
- Hover a mark to read SFCC Logs: 328 occurrences, last 2 min ago
- Click it to list the line's issues and select one in Issues. Open in Log Center selects the issue, or shows the events of all of them
- A grey mark means you changed the line after the log was written
When marks show, how they follow your edits and how they reach the Problems tool window, see Errors in the gutter
Fix with an AI agent
With B2C MCP, an AI agent such as Claude Code, Codex or Cursor works with the Log Center from the IDE. Ask "Check the sandbox for errors": the agent runs intellijsfcc_issue_triage, which ranks the open issues and finds the line in your project behind each. It can also parse and tail logs, compare before and after a deploy, find anomalies, write reports and mark issues fixed, see What Agents Can Do
Through the IDE's MCP server
With the IDE's MCP Server plugin on, AI agents connected to the IDE can also read the Log Center and mark issues fixed
| Action | What it copies |
|---|---|
| Investigate with MCP in an issue's details | A prompt that has an agent investigate this issue with the Log Center's tools |
| Copy Agent Fix Workflow in the gear menu | A prompt that has an agent fix the Log Center's issues through the IDE's MCP server |
Paste the prompt into an agent connected to the IDE's MCP server. The agent can use these tools:
| Tool | What it does |
|---|---|
intellijsfcc_logs_center_instances | Lists the instances with stored logs |
intellijsfcc_logs_center_search | Searches events by text, level and time |
intellijsfcc_logs_center_issues | Lists issues by count, latest or severity |
intellijsfcc_logs_center_issue_details | Reads one issue with its recent events |
intellijsfcc_logs_center_occurrence_context | Reads the entries around one event |
intellijsfcc_logs_center_timeline | Counts events over time |
intellijsfcc_logs_center_mark_fixed | Marks an issue fixed or not fixed |
intellijsfcc_logs_resolve_stack_source | Finds the project file of a stack frame |
- Investigate with MCP puts the prompt on the clipboard and says so. Copy Agent Fix Workflow says Fix workflow copied
- Secrets in the answers are masked
- Without the MCP Server plugin, both actions are disabled, and their tooltips read Turn on the MCP Server plugin so AI agents can use the Log Center