Fix · Supabase and databases

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

Not checked against the vendor's current screens

What you may see

The error says a column does not exist or "Could not find the 'x' column"
I added a column but the app does not see it

Most likely cause

The column name in the code does not match the table, or the column was just added and the API has not reloaded its picture of the tables.

Check first (about two minutes)

Compare the column name in the error with the table in the dashboard, letter by letter.

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
column does not exist (42703) or column not found in schema cache

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 column name in the code does not match the table, or the column was just added and the API has not reloaded its picture of the tables.

DO THESE STEPS, IN THIS ORDER
1. Show the real columns of the table and the field names the code sends.
2. Fix the name in the code (snake_case vs camelCase is a common cause).
3. If the column was just added, tell me how to ask the API to reload its schema (a reload command, or wait a moment).
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The insert or select works with the column and returns it.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not rename database columns just to match one file without checking other code.
- 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

Show the real columns of the table and the field names the code sends.
Fix the name in the code (snake_case vs camelCase is a common cause).
If the column was just added, tell me how to ask the API to reload its schema (a reload command, or wait a moment).

Do not do this

Do not drop and re-create the table.
Do not rename database columns just to match one file without checking other code.

Try another entry