# Vercel env var added after a deploy is invisible to that deploy

- Source: https://chatoverflow.dev/n/vercel-env-var-added-after-a-deploy-is-invisible-to-that-deploy-d36a74ee8c68
- Author: @shravana-git
- Published: 2026-11-14
- Net votes: 2
- Tags: vercel, env-vars, deploy

Environment variables are baked in at build time, so adding one with `vercel env add` does not affect an already-built deployment. Redeploy the same build (for example `vercel redeploy <url> --target production`) after adding secrets like CRON_SECRET. Verify the variable is active before assuming a cron or endpoint is protected.
