deployment_not_found

• An inspect, promote, or alias command returns deploymentnotfound or a 404 with that code. - A production or preview url that worked before now returns a platform 404 page. - A pipeline step that looks up a deployment by a stored id fails while newer deploys succeed.

Get the id from the source, not from memory. Open the deployment list for the project in the dashboard or run the platform list command for that project. Expected: you can see the deployments that actually exist, with their ids, urls, and states.

Compare the failing id character by character. Stale ids from an earlier deploy, a copied preview url, and ids trimmed by a shell variable all produce this exact 404. Success check: the id in your command or alias config matches an id in the list from step 1, or you have confirmed it is absent.

Check team and project scope. Deployment ids are scoped, so querying under the wrong team, the wrong project, or a personal account instead of the team returns not found even when the deployment is healthy. Switch to the team and project shown in the dashboard for that deployment and retry. Expected: the inspect or lookup call returns the deployment details.

Check the deployment state. A canceled, failed-early, or deleted deployment, and preview deployments removed by retention cleanup, cannot be inspected or aliased. In the dashboard, open the project history and look for a deleted or canceled entry at the time the link worked. Success check: you know whether the record still exists.

Redeploy if the record is gone. Run a fresh deploy for the same commit or branch, note the new deployment id and url from the output, and update any alias, bookmark, or pipeline variable that pointed at the old one. Expected: the new url serves the site and the alias resolves to the new deployment.

For CLI lookups, pass the url you just verified. Inspect commands accept a deployment url or id from the current scope. Run the inspect command against the verified url from step 5 (or step 1). Success check: it prints build and route details instead of the 404.

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

Problem query: deploymentnotfound

TL;DR: The platform has no deployment with that id in the scope you are querying, so lookups, inspect commands, and aliases pointing at it return 404. Copy the deployment id and url fresh from the deploy output or dashboard, confirm you are in the same team and project that created it, and check whether it was deleted, canceled, or replaced. If the record is gone, redeploy and re-point the alias; no setting restores a deleted deployment.