Search blocks by description or jump to a page.
A master list of grouped exceptions with event counts and sparkline bars beside a detail pane showing the selected issue and its stack trace.
The source for every Application block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Error Inbox is the exception triage surface for acme-app production, split into a grouped issue list and a detail pane. Filter chips across the top switch between Unresolved, Resolved, and Ignored. The list groups four exceptions by fingerprint, each row showing the error type, the message in monospace, the culprit frame, a 24 hour sparkline of event volume, and a footer of event count, affected users, and last seen. The selected TypeError opens on the right with an unresolved Badge, Resolve and Ignore buttons, three metric tiles, a stack trace whose in app frames are highlighted, and the failing line of code shown in context.
Issue groups, stack frames, and the code context are three typed const arrays. The expanded frame renders its source lines inline with the failing line tinted, so the crash is legible without opening the editor. Metadata Badges for release, browser, and runtime plus the assignee sit at the foot of the pane, and the footer notes that issues auto resolve after 14 quiet days and reopen on the next matching event.
Reach for this block on the monitoring or error tracking page, wired to your exception grouping backend and filtered to the active project. Point the Resolve and Ignore buttons at your issue state endpoint and keep the sparkline fed from the same event stream that raised the group.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the production error triage board. Other inbox variants:
Tip: the inline failing line is what saves the trip to the editor; keep the surrounding context in the group so triage happens without a context switch.