Runtime error logs
What is actually failing in production right now.
Overview
Pulls the last 24 hours of runtime errors from your Supabase project, aggregated by SQLSTATE and HTTP status, then cross-references the code paths that produce them. Counts and codes only — no raw log lines, query text, or user data leaves your project.
What it looks for
- RLS denial spikes (SQLSTATE 42501)
- Connection-pool exhaustion (53300)
- Statement timeouts and slow-query signals (57014)
- Repeated constraint violations
- API 5xx spikes, tied back to the route that raised them
Why it matters
A spike in 42501 permission-denied errors is either a policy you broke on the last deploy or someone probing your tables, and both deserve attention today. Connection-pool exhaustion and statement timeouts show up here well before users start reporting them.
Rules in this check
| What it reports |
|---|
| RLS-denial spike |
| Connection-pool exhaustion |
| Statement-timeout/slow-query |
| Repeated constraint violations |
| API 5xx spike |
How the fixes arrive
Findings from this check are graded when the scan runs, so the fix path is chosen per finding rather than fixed per rule. Low-risk changes arrive as a pull request you review, changes that need confirming against your live config arrive as a draft, and the rest as a step-by-step guide.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.