Skip to main content

Debug

The System Admin Debug tab provides a small set of diagnostics and deliberate Sentry test controls. It is not a full health dashboard or log viewer.

Environment information​

The page displays:

  • application mode;
  • whether a Sentry DSN is configured;
  • Supabase URL;
  • application version, when set.

Use this information to confirm which environment and build you are viewing before investigating a report.

Do not copy environment screenshots into public channels; URLs and version details can be operationally sensitive.

Send a Sentry test message​

  1. Tell the monitoring owner you are about to test.
  2. Record the current time, environment and app version.
  3. Select Send test message.
  4. Confirm the on-screen acknowledgement.
  5. Check the intended Sentry project for the informational event.

This verifies that the browser attempted to capture a message. It does not validate every backend, release or alerting integration.

Throw a test error​

Deliberate error

This control intentionally raises an error so the application error boundary and Sentry capture path can be tested. Use it only in a controlled window.

  1. notify anyone observing the environment;
  2. record the timestamp;
  3. select Throw test error;
  4. observe the error experience;
  5. verify the event in Sentry;
  6. reload or return to the application as needed.

Do not repeatedly generate test errors in production. A successful test can trigger normal alerting and affect operational metrics.

What the tab does not test​

  • database read/write health;
  • Gemini or LiveKit availability;
  • email delivery;
  • object storage;
  • MCP OAuth;
  • provider billing;
  • edge-function deployment parity;
  • alert routing beyond event capture.

Use feature-specific smoke tests and operational dashboards for those systems.

Diagnostic handoff​

When escalating a problem, include:

  • environment mode;
  • app version;
  • UTC/local timestamp and timezone;
  • affected company and role, without unnecessary personal data;
  • route and action;
  • exact visible error;
  • whether a Sentry test message arrived.

Never include session content, tokens, credentials or private keys in a ticket unless an approved secure process requires it.

Troubleshooting​

Sentry shows “Not set”​

Client error reporting is not configured for that build. Do not expect test events to arrive; escalate configuration through the deployment process.

Test message is absent​

Confirm the correct Sentry project/environment, allow for processing delay, and check network/privacy blockers. Record the app version before further tests.

App version is “Not set”​

The build did not receive version metadata. Use deployment records and environment mode to identify it, then correct the release pipeline separately.

Supabase URL is unexpected​

Stop destructive administration. Verify the environment before continuing.

Last updated on