Fix · Supabase and databases

"Could not find the table in the schema cache" (PGRST205)

Not checked against the vendor's current screens

What you may see

A new table exists in SQL but the API says it cannot find it

Most likely cause

The data API keeps a copy of the table list and did not refresh yet, or the table is in a schema the API does not expose.

Check first (about two minutes)

Wait one minute and retry; then check the table is in the public schema.

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a careful senior engineer who knows Supabase (database, login and file storage) and explains it to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

Menu and button names change over time. If you cannot find a button or page I mention, say so and tell me what to look for instead of guessing.

THE PROBLEM
"Could not find the table in the schema cache" (PGRST205)

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
The data API keeps a copy of the table list and did not refresh yet, or the table is in a schema the API does not expose.

DO THESE STEPS, IN THIS ORDER
1. Confirm the table or function exists in the schema the API exposes.
2. Ask the API to reload its schema (the documented reload notification) as part of the migration, and tell me exactly what to run.
3. Check the function's argument names match the call.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The same call now finds the table or function.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not move the table to another schema without telling me.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Confirm the table or function exists in the schema the API exposes.
Ask the API to reload its schema (the documented reload notification) as part of the migration, and tell me exactly what to run.
Check the function's argument names match the call.

Do not do this

Do not expose a private schema to the API to fix this.
Do not move the table to another schema without telling me.

Fix it column does not exist (42703) or column not found in schema cache

Try another entry