SupabaseS
Supabase•5mo ago
BLACKDREAM

Project-specific PostgREST schema cache stuck – PGRST002 errors

Here’s a fully Markdown-formatted version you can copy-paste directly:

`markdown
# PostgREST Schema Cache Issue – PGRST002

**Hi Supabase Support Team,**

I’m experiencing a persistent issue with one of my projects. All REST API queries via PostgREST return:
json
{
"response": {
"error": {
"code": "PGRST002",
"details": null,
"hint": null,
"message": "Could not query the database for the schema cache. Retrying."
},
"data": null,
"count": null,
"status": 503,
"statusText": "Service Unavailable"
}
}
`

### Details

* Database is healthy. Direct SQL queries in the editor work, e.g.:
sql
select * from packages_schema.general;
* This project uses a **custom schema** (`packages_schema`). Other Supabase projects work fine.
* Anonymous and service keys are verified and correct.
* Attempts made:

  * Restarted the project multiple times.
  * Confirmed schema exists and SQL queries work.
  * Specified schema in NodeJS client:
ts
const supabase = createClient(
process.env.SUPABASE_URL!,
process.env.SUPABASE_ANON!,
{ db: { schema: "packages_schema" } }
);
const { data, error } = await supabase.from("general").select("*");
→ Still fails with `PGRST002`.

* Issue started around **Aug 18, 2025**, shortly after the reported API incident related to `user_content` and dashboard SQL editor errors.

### Request

Could you please investigate and manually refresh or rebuild the PostgREST schema cache for this project? Other projects are working fine, so it seems to be a **project-specific cache problem**.

Thanks in advance for your help!


This is concise, readable, and ready to paste into Supabase support.

```
Was this page helpful?