Filters
Narrow captured exceptions by date range (UTC), source, exception type, service, tenant id, or user id, or search the message, type, and fingerprint text. Source is usually the quickest way in: it scopes the list to one layer.
Super AdminAvailable
Exceptions
The platform-wide error console. Every layer reports here: the API, background jobs, outside integrations, and the web, desktop, mobile, and embedded apps. Each problem arrives with protected diagnostic context so administrators can investigate it in one place.
What you can do here
Exception list & detail
Each entry carries the error, where it happened, and who was affected. Open one for the stack trace and sanitized payload artifacts.
Artifacts
Full diagnostic artifacts download via short-lived links. Detail views and downloads are themselves audited.
Copy for troubleshooting
Tick one or more exceptions and copy them as a single report. Each one carries its complete stack trace, its context, and its recorded details, clearly separated so they stay distinguishable once pasted into a ticket, a chat, or a debugging tool. Request and context payloads stay out unless you ask for them, because they can reference patient data.
Delete & cleanup
Permanently remove an exception once it is resolved or confirmed noise: deletion clears its searchable record and every stored artifact. Delete one from its row or its detail view, tick rows (or select all loaded) to remove a batch, or use Delete all to clear every captured exception in one pass while a progress bar tracks it.
Follow these steps
Investigate a failure
- Filter by the day and the source layer where the problem was reported, then narrow by service if you need to.
- Open the exception to read the stack and context.
- Download artifacts only when the summary is not enough; access is audited.
Share a failure with someone else
- Tick the exceptions you want, or use the header checkbox to take every loaded row, then choose Copy details.
- Copying reads the complete stack trace for each one, so a long selection takes a moment and shows its progress.
- Turn payloads on only when the failure cannot be understood without them, and treat the pasted text as patient data when you do.
- If your browser blocks the copy, the report appears in the dialog ready to select and copy by hand.
Clear out resolved noise
- Delete an exception from its row or detail view once the defect is fixed or it is confirmed noise.
- To clear many at once, tick the rows or use the header checkbox to select all loaded, then choose Delete selected.
- To wipe the console entirely, choose Delete all: it finds every captured exception across the retention window, confirms the count, then deletes in batches while a progress bar tracks it. You can stop between batches.
- Deletion is permanent, removes the stored artifacts too, and is audited like every other action here.
Helpful habits
- Triage by recurrence first: one user hitting an error ten times and ten users hitting it once are different problems.
- Artifacts can reference patient-linked payloads; handle them like PHI and let the 90 day retention do its job.
- A copied report holds the same protected detail as the console, so paste it somewhere allowed to hold it.
- Prefer the automatic 90 day expiry for anything you might still need; reach for delete to remove resolved defects or noise, not as routine cleanup.
Tips
- Expected denials (401/403) are never captured; if you see one here, something upstream mislabeled it.
- Copy details reads the full stack trace rather than the shortened one shown in the table, so what you paste is the whole trace.
- Records expire automatically after 90 days, matching the artifact bucket lifecycle.
- Delete all ignores the filters on purpose: it clears every captured exception across the retention window, not just the rows in view.
- Deletion is permanent: the record and its artifacts are removed, not archived, and each delete is written to the audit trail.