Fix · Vercel and deploying

I changed an environment variable but nothing changed

Not checked against the vendor's current screens

What you may see

The live site still uses the old value
A key I rotated still fails on the website

Most likely cause

Variables are read when a deployment is built or started; an existing deployment keeps the old value until you redeploy, and browser variables are baked in at build time.

Check first (about two minutes)

Check the time of the last deployment against the time you changed the variable.
Check the variable was saved for the Production environment (not only Preview).

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
I changed an environment variable but nothing changed

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
Variables are read when a deployment is built or started; an existing deployment keeps the old value until you redeploy, and browser variables are baked in at build time.

DO THESE STEPS, IN THIS ORDER
1. Confirm the variable name in the code matches exactly and which environments have it.
2. Tell me how to trigger a fresh deployment of the latest commit (the redeploy action on the deployment, or a new empty commit) without using the old build cache if needed.
3. After the new deployment is Ready, test the exact feature that used the variable.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The live site works with the new value (check the feature, not the value itself).
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not print the variable value in a page or a log to check it.
- 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 variable name in the code matches exactly and which environments have it.
Tell me how to trigger a fresh deployment of the latest commit (the redeploy action on the deployment, or a new empty commit) without using the old build cache if needed.
After the new deployment is Ready, test the exact feature that used the variable.

Do not do this

Do not hard-code the new value in the code.
Do not print the variable value in a page or a log to check it.

Try another entry