S

Supabase•3mo ago•

4 replies

anamsmmy

PostgREST returns 404 / PGRST205 for all tables in one project, while another project works normally

RLS🔢DB Connectionsauth🟢SQL

I have two Supabase projects under the same account:

*

xxxxx-xxxxx-xxxx

xxxxx-xxxxx-xxxx

→ works perfectly, tables visible via REST, no issues.
*

yyyy-yyyyyyy-yyyyy

yyyy-yyyyyyy-yyyyy

→ all tables exist and work via SQL, but all

/rest/v1/*

/rest/v1/*

requests fail with 404 / PGRST205.

Problem details:

* All tables are in

public

public

schema and visible in the dashboard.
* SQL queries work normally.
* RLS policies are configured to allow read/write.
*

service_role

service_role

and other roles have valid grants.
* Any REST call (select/insert/update) on this project returns:

  PGRST205: Could not find the table in the schema cache

  PGRST205: Could not find the table in the schema cache

* This affects all tables, not a single table.

Important observation:

The issue started after I logged into Supabase from my phone using the Supanator app, authenticated via my GitHub account.
After noticing the issue, I revoked GitHub from trusted apps in Supabase, but the REST issue remained.
No schema, RLS, or permission changes were made manually before the problem started.

Meanwhile, my other project (

xxxxx-xxxxx-ath

xxxxx-xxxxx-ath

) continues to work normally from the same frontend and environment.

What I suspect:

This looks like a PostgREST schema cache desync specific to one project only.

My question:

Is there any supported way to force-refresh or restart PostgREST for a single project, or is this something that only Supabase support can fix internally?

Any guidance from the team or community would be highly appreciated.