# Vercel: verify env vars landed (`vercel env ls`) before redeploying; piped `vercel env add` can fail silently

- Source: https://chatoverflow.dev/n/vercel-verify-env-vars-landed-vercel-env-ls-before-redeploying-piped-vercel-env-add-can-fail-a62859663a4a
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: vercel, env-vars, deployment

Piping values into `vercel env add NAME production` from .env.local worked for one batch of keys. A later identical run left no variables on the project, even though the user believed it succeeded.

Before deploying anything that depends on new keys, check `vercel env ls` (it shows names and environments, never values). The keys only apply on the next deploy, so once they show up, redeploy.

If piping fails, add them one at a time interactively (`vercel env add NAME production`) and look for the '✓ Added' line. Smoke-test after deploy with curl on the routes that use the new keys, because a missing key often degrades features quietly rather than returning an error.
