Turn a Supabase PGRST204 schema-cache error into a launch packet.

Paste redacted PostgREST error notes and check whether the new column/table/function is proven in the same project, the Data API schema cache was reloaded safely, and the issue is not actually a wrong-project, exposed-schema, grants, RLS, or generated-migration problem.

Build packet See fixed-scope report

Prove the database firstRecord a redacted SQL check showing the column or table exists in the same project the REST request hits.

Separate cache from permissionsPGRST204 is different from a 42501 grant/RLS failure, so the packet keeps them apart.

Reload without guessingCapture NOTIFY pgrst, PostgREST version, and queue-refresh evidence before disruptive restarts.

Project label

Context

Redacted error and migration notes Evidence already captured

REST URL/project reference matches the project where SQL was changed SQL proves the new column/table/function exists in the target schema REST select() or equivalent read confirms whether PostgREST sees the new shape NOTIFY pgrst, 'reload schema' was run after the committed DDL select pg_notification_queue_usage() was run for stale notification-queue evidence PostgREST/Data API version or infrastructure upgrade path was checked API-exposed schema setting and grants/RLS were checked separately The migration is replayable from a clean local/staging reset

This page runs locally in the browser. Paste only redacted notes. Do not paste database URLs, passwords, JWT secrets, service-role keys, project secrets, real user rows, private screenshots, payment data, full names, private handles, or private account records.

Ready.

Want a 24h second pass on this schema-cache packet?

If the checker finds several launch-critical gaps, the fixed-scope Supabase report can review one redacted packet: migration notes, REST errors, same-project proof, schema-cache reload evidence, grants/RLS separation, and next smoke tests.

Check paid report scope Read sample report

Schema-cache review packet

What this checks

Wrong-project evidence: REST URL/project reference and SQL Editor target must describe the same project.
Database evidence: information_schema.columns, pg_proc, or a direct SQL query proves the new object exists.
PostgREST evidence: PGRST204, missing column/table/function text, and a REST select() probe show what the Data API sees.
Reload evidence: NOTIFY pgrst, 'reload schema', committed DDL timing, notification queue refresh, and version/infrastructure checks.
Non-cache problems: schema exposure, grants, RLS, generated db pull replay, and broad grants are handled as separate launch checks.

Source-backed notes

Supabase troubleshooting Supabase documents stale PostgREST schema-cache behavior and a non-disruptive notification queue refresh check. PostgREST schema cache PostgREST documents schema-cache reloads with signals, NOTIFY pgrst, and event triggers. Public issue evidence Open Supabase issue #42183 describes PGRST204 after adding columns, including same-project and cache-reload triage.