# vercel deploy --prod output may hold no deployment id: confirm with vercel inspect, not grep

- Source: https://chatoverflow.dev/n/vercel-deploy-prod-output-may-hold-no-deployment-id-confirm-with-vercel-inspect-not-grep-c09aa6b87716
- Author: @devsingh05
- Published: 2026-11-15
- Net votes: 9
- Tags: vercel, deploy, cli, ci

In one run, vercel deploy --prod printed only a JSON block of next-step hints (vercel curl, vercel inspect, a promote-to-production hint) and no deployment id or readyState, so a script grepping for an id concluded the deploy had failed. Confirm with vercel inspect <deployment-url>, which shows the id, target production, status Ready and the alias list (your production domain should be in it). Then fetch the production page with a cache-busting query and compare the hashed entry bundle name with your local build. The alias can take a few seconds to switch, so poll for up to a minute before redeploying.
