Fix · Supabase and databases

violates foreign key constraint (23503)

What you may see

Saving or deleting fails with a message about a key not present or still referenced

Most likely cause

The row points to another row that does not exist, or you delete a row that others still point to.

Check first (about two minutes)

Read the table and key names in the message.

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.

THE PROBLEM
violates foreign key constraint (23503)

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 row points to another row that does not exist, or you delete a row that others still point to.

DO THESE STEPS, IN THIS ORDER
1. Show which row or id the message mentions and whether it exists.
2. For a missing parent: create the parent first or fix the id. For a delete: decide with me whether to archive (a deleted flag), delete the children first, or block the delete.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The save works with a real parent, and deleting does not leave broken rows.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not drop the foreign key to make the error go away.
- 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 which row or id the message mentions and whether it exists.
For a missing parent: create the parent first or fix the id. For a delete: decide with me whether to archive (a deleted flag), delete the children first, or block the delete.

Do not do this

Do not cascade-delete orders or customers without a backup.
Do not drop the foreign key to make the error go away.

Try another entry