Log Center keeps track of what you already handled. Mark an event fixed once the change is out, park the ones you will handle later in a backlog, and let Anomalies point at what changed. Open errors stay in the Problems panel next to your code, and a copied prompt lets your AI agent work through them with the SFCC MCP tools
Mark events fixed
Check the Fixed box of an event, or use Mark event fixed, when its fix is in place. The event closes its drawer, leaves the Problems panel, and Log Center confirms Log Center event marked fixed and removed from diagnostics. Uncheck it, or use Reopen event, to bring it back
- Include fixed in the Workflow filters shows or hides fixed events. It is on by default
- A fixed event that keeps occurring is not reopened silently. It shows in Anomalies as a Regression, with how many times it occurred since the fix
- Fixed marks are saved in the local database of the instance and survive a restart, and a reparse with Read from beginning keeps them
Keep a backlog
Add event to backlog parks an event you will handle later, and Remove event from backlog takes it out. The Backlog filter cycles through three states:
| Filter | Shows |
|---|---|
| Backlog: all | Every event |
| Backlog: hidden | Events outside the backlog, so the list shows what still needs a decision |
| Backlog: only | Only the backlog |
Anomalies
Anomalies compares a recent window with the logs collected before it, and lists what is unusual:
| Window | Compares |
|---|---|
| 1H | The last hour with the previous 7 hours |
| 24H | The last 24 hours with the previous 7 days |
| 7D | The last 7 days with earlier parsed history |
| Range | The time range selected on the Events page |
| Kind | Means |
|---|---|
| Regression | The event was marked fixed, but it kept occurring after the fix |
| New error | The event appears for the first time in the window |
| Returned | The event is back after a long quiet period |
| Spike | Far more occurrences than expected, such as 42 events vs ~3 expected (14×) |
| Burst | Most occurrences fall into a short time span |
| Spreading | The event spread to new sites or endpoints |
| Stopped | An event that used to occur has stopped. It is marked Resolved? |
Each anomaly shows its severity, a sparkline, and its incident windows. Events filters the table to that event, and Report… starts a report of the detected anomalies. With nothing unusual, the panel says so. Anomalies need an instance, so pick one first
Problems diagnostics
Open errors and warnings that map to a file in your workspace appear in the Problems panel, with the source Intellij SFCC Logs:
SFCC log error: Cannot read property "ID" from null (12 occurrences, latest 2026-10-10 14:32:07.418 GMT)
Log files: error-blade1-2-appserver-20261010.log
First seen 2026-10-10 09:14:55.102 GMT
Latest occurrence 2026-10-10 14:32:07.418 GMT
Sites: RefArch (12)- Only ERROR and WARN events that are not fixed and resolve to a workspace file get a diagnostic. Other events stay in Log Center
- The related information lists the log files, first and latest occurrence, sites, sessions, and the request id
- Diagnostics follow your edits, and they are mapped again when files change or you switch Git branches
- Marking an event fixed removes its diagnostic
Hand off to your AI agent
Two Workflow buttons prepare the work for an agent that has the SFCC MCP server:
| Button | What it copies |
|---|---|
| Copy fix prompt | SFCC MCP Log Center Fix Workflow, an 11 step loop: search the open errors and warnings by frequency, read each issue, check route overrides, fix the source, validate it with diagnostics, and mark it fixed only with validation evidence. Log Center confirms Copied SFCC MCP Log Center fix workflow. |
| Investigate with MCP | An investigation prompt for the instance and the current filters. The dialog shows the Captured scope, and Copy investigation prompt copies it |
Paste the prompt into your agent chat. The agent reads the same events through the MCP tools, so it does not need log text pasted into the chat
MCP tools for logs
| Tools | What the agent can do |
|---|---|
intellijsfcc.logs.center.search, issue_details, occurrence.context, timeline, compare, anomalies, instances | Search events, read an issue with its occurrences and source, chart it over time, compare windows, and list anomalies and instances |
intellijsfcc.logs.center.mark_fixed | Mark an issue fixed with a reason and validation evidence |
intellijsfcc.logs.center.investigation | Prepare an investigation dataset for the instance, review event groups, and record conclusions without marking anything fixed |
intellijsfcc.logs.center.reports.generate, status, read, list, cancel | Create and read Log Center reports |
intellijsfcc.logs.list, read, search, errors, report, analyze_entry, resolve_stack_source, redaction.preview | Work with log files and single entries directly |
intellijsfcc.logs.watch.start, watch.stop, clear.plan, clear.execute | Start and stop tails, and clear data after you confirm |