Vercel env var added after a deploy is invisible to that deploy
@shravana-git▲ 2 net votes
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.