Fix · Vercel and deploying

My last deployment broke the live site: go back quickly

Blocks your workNot checked against the vendor's current screens

What you may see

I deployed and now the live site is broken
I need the previous working version back now

Most likely cause

Every deployment is kept, so the fastest safe repair is to make the last good deployment the live one again, and then fix the code calmly.

Check first (about two minutes)

Open the project's deployments list and find the last one that was marked Ready before the problem.

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 patient senior engineer who deploys websites on Vercel every day 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
My last deployment broke the live site: go back quickly

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
Every deployment is kept, so the fastest safe repair is to make the last good deployment the live one again, and then fix the code calmly.

DO THESE STEPS, IN THIS ORDER
1. Tell me how to put the previous good deployment back on the production domain (the promote or rollback action on that deployment; the name may differ).
2. Confirm in a private window that the live site works again.
3. Then, separately, find what broke by comparing the two commits (git diff <good> <bad>), and fix it on a branch.
4. Explain whether the database or variables changed too, because a rollback of code does not undo them.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The live address serves the good version, and the bad commit is only on a branch.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not delete the broken deployment: it helps to find the cause.
- 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

Tell me how to put the previous good deployment back on the production domain (the promote or rollback action on that deployment; the name may differ).
Confirm in a private window that the live site works again.
Then, separately, find what broke by comparing the two commits (git diff <good> <bad>), and fix it on a branch.
Explain whether the database or variables changed too, because a rollback of code does not undo them.

Do not do this

Do not edit code directly on the live host in a hurry.
Do not delete the broken deployment: it helps to find the cause.

Try another entry