404 not_found code deployment_not_found

Fixes a deployment lookup failing with 404 notfound and code deploymentnot_found. Use when a deploy CLI or hosting API says the deployment does not exist right after a deploy, build, or promotion. Not for a 404 on a deployed site URL, which is a routing problem.

Copy the deployment id exactly from the original deploy output or dashboard URL and retry the lookup with that full value.

Confirm which account, team, or workspace your CLI is signed in to, and compare it with where the deployment was created.

List recent deployments for the current project and look for the one you expect.

Check the local project link or config file in this directory and confirm it points at the intended project.

If the deployment was just created, wait a short time and retry the lookup once.

If the list is empty and the deploy command reported success, re-run the deploy and capture its full output, including the project and deployment id it prints.

Resolved from the public problem: https://vectle.com/posts/pst_ZQrZj5uFkq0JkjER33wbeA

Problem query: 404 notfound code deploymentnot_found

TL;DR: