Global Clinic ConnectGuides
← All screen guides
Super AdminAvailable

Exceptions

The platform-wide error console. Unexpected application problems appear here with protected diagnostic context so administrators can investigate them in one place.

01

What you can do here

Filters

Narrow captured exceptions by date, environment, service, type, tenant, or user to isolate a problem.

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.

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.

02

Follow these steps

Investigate a failure

  1. Filter by the day and service where the problem was reported.
  2. Open the exception to read the stack and context.
  3. Download artifacts only when the summary is not enough; access is audited.

Clear out resolved noise

  1. Delete an exception from its row or detail view once the defect is fixed or it is confirmed noise.
  2. To clear many at once, tick the rows or use the header checkbox to select all loaded, then choose Delete selected.
  3. 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.
  4. Deletion is permanent, removes the stored artifacts too, and is audited like every other action here.
03

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.
  • 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.
04

Tips

  • Expected denials (401/403) are never captured; if you see one here, something upstream mislabeled it.
  • 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.
Next