Summary
Two error-severity Postgres log entries appeared in the Helm-Production Supabase project (qmnssrrolpinvwjjnufo) within ~17s of each other, surfaced by the automated Mission Control error sweep.
Errors
| Time (UTC) |
Severity |
Message |
| 2026-07-03 02:04:06 |
ERROR |
column "expires_at" does not exist |
| 2026-07-03 02:04:23 |
ERROR |
relation "public.rate_limits" does not exist |
Triage pointers
- The application uses
auth_rate_limits (confirmed healthy — heavy successful read/write traffic in the same window from the login-lockout / idle-session flow). There is no reference to a bare public.rate_limits table anywhere in src/ (grep clean), so the query most likely originates from a dependency, an edge function, a DB function/trigger, or an external probe — not first-party app code.
expires_at is a valid column on many tables; this error implies a query hit a relation that lacks it (plausibly the same missing/renamed rate_limits relation).- Both fired via the authenticated
postgres connection path (not the REST API), 17s apart — likely one code path.
- Source: Supabase Postgres logs, project
qmnssrrolpinvwjjnufo (Helm-Production).
Impact
Unknown — no correlated user-facing errors in Sentry or Vercel this window; the auth rate-limit + idle-session features (which use auth_rate_limits) are functioning. Likely a secondary/best-effort path failing silently, or an external scanner.
Notes
Filed automatically by the Mission Control error sweep. Not auto-resolved. Do not assume first-party until the calling site is identified.
🤖 Mission Control — error sweep 2026-07-03
Summary
Two error-severity Postgres log entries appeared in the Helm-Production Supabase project (
qmnssrrolpinvwjjnufo) within ~17s of each other, surfaced by the automated Mission Control error sweep.Errors
column "expires_at" does not existrelation "public.rate_limits" does not existTriage pointers
auth_rate_limits(confirmed healthy — heavy successful read/write traffic in the same window from the login-lockout / idle-session flow). There is no reference to a barepublic.rate_limitstable anywhere insrc/(grep clean), so the query most likely originates from a dependency, an edge function, a DB function/trigger, or an external probe — not first-party app code.expires_atis a valid column on many tables; this error implies a query hit a relation that lacks it (plausibly the same missing/renamedrate_limitsrelation).postgresconnection path (not the REST API), 17s apart — likely one code path.qmnssrrolpinvwjjnufo(Helm-Production).Impact
Unknown — no correlated user-facing errors in Sentry or Vercel this window; the auth rate-limit + idle-session features (which use
auth_rate_limits) are functioning. Likely a secondary/best-effort path failing silently, or an external scanner.Notes
Filed automatically by the Mission Control error sweep. Not auto-resolved. Do not assume first-party until the calling site is identified.
🤖 Mission Control — error sweep 2026-07-03