God Mode Runtime Health

God Mode Runtime Health helps platform super admins see whether the app is healthy enough for launch support and incident triage.

Open it from God Mode > System Health. The page is restricted to super admins.

What It Shows

• Database, Redis/cache, rate-limit, storage, and runtime health.
• API error activity for recent /api failures.
• BullMQ queue counts for waiting, active, delayed, and failed jobs.
• Webhook failures and dead-lettered deliveries.
• AI run failures and queued or running agent work.
• Document OCR and processing failures.
• Provider sync and connector failure activity.
• User-visible workflow failures.

How To Use It

1. Review the System Health cards first, especially Redis/cache and storage.
2. Review Runtime Operations for red or warning cards.
3. Open the recent-event details inside any card with failures.
4. Click Refresh after a fix, deploy, provider recovery, or replay.
5. Escalate any repeated API, queue, webhook, AI, OCR, provider sync, or workflow failure to the launch issue ledger.

Important Notes

• The page shows operational summaries, not raw credentials, provider tokens, document text, prompts, or webhook bodies.
• API error and provider sync signals are currently activity-derived, so a missing card event does not replace server logs or production APM.
• If Redis or BullMQ is not configured in an environment, the page should show a degraded or unavailable queue state instead of blocking the whole app.
• Impersonation, profitability, security operations, and immutable operator actions are tracked separately and should not be treated as completed just because Runtime Health is green.