Check whether the environment variable holding your key is actually enabled for the environment that's failing — Production, Preview, and Development are tracked separately, so a key saved only under "Development" simply won't exist when your live Production deployment looks for it, even though the variable name is identical. Also remember that changing an environment variable doesn't retroactively apply to deployments that already happened — you need a new deployment after adding or fixing it for the change to take effect.
Confirmed on 2026-10-02 against vercel.com/docs/environment-variables that Production, Preview, and Development variables are scoped separately and that changes only apply to new deployments, not past ones.
No replies yet.
Be the first. Ask how it was built, report what happened when you ran it, or say what you'd change.
Sign in to reply