06Error tracking

One issue

Click an issue on Issues to open it. The page reads the last 7 days.

The header

The header names the issue: its type, its state, the error message, and the file and function it comes from, with the page. A Fatal, Warning or Info badge shows when the sender gave the error a level other than error. A line says whether the issue is handled or unhandled, when it was first and last seen and which release it came in. See Report your own errors for how levels and handled work.

  • Assign gives it to a person. An issue you assign stays theirs, and otherwise ownership rules decide.
  • Ignore mutes it.
  • Resolve, or Resolve in next release when the issue has a release, marks it fixed. A resolved issue that fires again becomes Regressed.
  • Reopen appears on a resolved or ignored issue.

Impact

A chart of the last 7 days by the hour, with the release marked, beside four figures:

FigureWhat it shows
EventsHow many times it fired, and the rate per hour.
PeopleThe distinct visitors who hit it, and how many were customers.
Revenue at riskWhat the visits that stopped after this error would have earned: their number times what visits to the same pages without the error earn.
Kept goingThe share of visits that went on to another page or a purchase after the error, against visits to the same pages without it.

Who it hurts splits the people into Customers, In trial and Visitors.

Hand off the fix has Copy fix prompt, a prompt for your coding agent with the error, where it happens, the stack and what the visitor did just before it, in the same format as the install hand-off. Open in Cursor opens it there, and it works with Claude Code too.

What people said

When people wrote about this error through the feedback widget, the latest three notes show here, each with its screenshot, who sent it and when. Click one to open the note. Resolving the issue marks its open notes done and emails the people who asked to hear when it's fixed.

Likely cause

Where it is available, the card also offers Find the likely cause. SnowAnalytics has Claude read the stack, the code around the failing line, the breadcrumbs and a typical visit, and the card then becomes Likely cause: a plain explanation and, when it is confident of a minimal fix, the change as a diff. The reading is kept for that issue and release, so it is written once. It needs code to read, so an issue with no stack to go on doesn't offer it. Where it isn't available, the card stays Hand off the fix. Treat the cause as a lead to check, not a verdict.

Stack trace

The stack trace shows the code around the failing line, with the line marked. Your code folds the library frames behind a line, and Full trace shows every frame in order. Copy copies the stack. The card says where the stack came from: source-mapped from a release, or minified: no source map uploaded. Upload source maps to read your own code. Server errors arrive with their own source lines, so they need none.

Below the stack, the breadcrumbs list what the visitor did in the 20 steps before the latest event: page changes, clicks, network calls and console warnings.

What people did

What they did replays a typical visit: the pages viewed, the clicks, the error, any rage clicks and how the visit ended. Beside the stack it is as tall as the stack card and scrolls inside, so a long visit never stretches the page. A click on script text, a selector or a whole block of text reads as the element it hit, such as Clicked a button, with its selector under it. Open this visitor's journey opens that visitor. Most common shows the browser, device, country and release most often behind the issue.

Affected people

The people it hit, the five with the most revenue at risk first, each with their photo from your identify call or a generated face, and marked Customer, Trial or Visitor. Their outcome says whether they Paid afterwards, Kept going or Left. Click one to open their profile.

If the issue won't load

An issue that was merged into another or removed shows We couldn't load this issue. Go Back to issues.

On this page