deployment_not_found

Not specified by the original author.

Short answer: the deployment your request points to does not exist. Open the project in the Vercel dashboard, copy the live deployment URL from there, and use that exact URL. `` DEPLOYMENT_NOT_FOUND `` 1. In the Vercel dashboard, open the project and confirm the deployment still exists. Deleted deployments and preview deployments from removed branches are gone for good. 2. Copy the deployment URL exactly from the dashboard and compare it character by character with the one you requested. Fix typos, stale IDs, or wrong paths. 3. If the deployment exists but will not load, open its build and runtime logs. A failed build leaves no servable output, and the logs show why. 4. Confirm your account still has permission to access the project. A lost or changed role produces the same not-found. Root cause: Vercel resolves the deployment reference before it resolves any route inside it. A bad reference fails at that first step, so no application code ever runs. When to use: API calls, webhooks, or browser hits that name a specific deployment and get this code. When NOT to use: 404s on routes inside a working deployment are routing problems, check rewrites in vercel.json, not the deployment reference. Variant phrasings: "vercel deployment not found error", "vercel 404 deploymentnotfound", "deployment not found vercel preview". Edge cases: preview URLs die with their branches. If you linked a preview URL somewhere durable, promote a production deployment and link that instead.

Context: DEPLOYMENTNOTFOUND is Vercel's 404 for a deployment reference. It fires when a request names a deployment that does not exist: the URL or deployment ID has a typo, points at a stale preview, or the deployment was deleted. It is about the deployment itself, not about a page inside your app.

Source: DEPLOYMENTNOTFOUND is Vercel's 404 for a deployment reference. It fires when a request names a deployment that does not exist: the URL or deployment ID has a typo, points at a stale preview, or the deployment was deleted. It is about the deployment itself, not about a page inside your app.

Verified resolution: Short answer: the deployment your request points to does not exist. Open the project in the Vercel dashboard, copy the live deployment URL from there, and use that exact URL. `` DEPLOYMENT_NOT_FOUND `` 1. In the Vercel dashboard, open the project and confirm the deployment still exists. Deleted deployments and preview deployments from removed branches are gone for good. 2. Copy the deployment URL exactly from the dashboard and compare it character by character with the one you requested. Fix typos, stale IDs, or wrong paths. 3. If the deployment exists but will not load, open its build and runtime logs. A failed build leaves no servable output, and the logs show why. 4. Confirm your account still has permission to access the project. A lost or changed role produces the same not-found. Root cause: Vercel resolves the deployment reference before it resolves any route inside it. A bad reference fails at that first step, so no application code ever runs. When to use: API calls, webhooks, or browser hits that name a specific deployment and get this code. When NOT to use: 404s on routes inside a working deployment are routing problems, check rewrites in vercel.json, not the deployment reference. Variant phrasings: "vercel deployment not found error", "vercel 404 deploymentnotfound", "deployment not found vercel preview". Edge cases: preview URLs die with their branches. If you linked a preview URL somewhere durable, promote a production deployment and link that instead.

Source URL: https://vercel.com/docs/errors/deploymentnotfound

• 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.

Not specified by the original author.

TL;DR

deploymentnotfound on Vercel means no deployment is attached to the hostname you opened: the error page shows 404 NOTFOUND with Code DEPLOYMENTNOT_FOUND. The domain was never assigned to the project, the deployment behind the URL was deleted, or the URL is a stale preview link. Fix it by attaching the domain in the project under Settings, Domains, or by promoting a Ready build to Production; redeploying alone does not attach a domain.

404: NOT_FOUND
Code: DEPLOYMENT_NOT_FOUND

Use this when

• A Vercel URL shows 404 NOTFOUND and the code line reads DEPLOYMENTNOT_FOUND
• A custom domain was bought and DNS points at Vercel, but the site never loads
• An old preview or deployment URL that used to work now returns 404

Not for this skill when

• The code is NOTFOUND without DEPLOYMENT in front of it: a deployment is serving but its routes have no match, which is a routing or output problem
• Your own app renders its 404 page: that is your code answering, not Vercel
• The deploy itself failed in the build log: fix the build first, then come back here if the hostname still 404s

Steps

1. Read the code, not just the 404. Open the failing URL and confirm the page shows DEPLOYMENTNOTFOUND, not plain NOT_FOUND.

Expected: you have confirmed which of the two Vercel 404s this is before changing anything.

2. Attach the domain to the project. In the Vercel dashboard open your project, then Settings, then Domains, type the domain and click Add. It takes effect within seconds and does not need a redeploy.

Expected: refreshing the URL loads your site instead of the error page.

3. Check you are opening the right URL. Preview URLs (project-git-branch-team.vercel.app) are ephemeral and die when the branch or project is deleted. Use the production domain, or click Visit on the latest deployment.

Expected: the production URL works even if the bookmarked preview URL does not.

4. Confirm a Ready production deployment exists. Open the Deployments tab. If the latest Production deployment shows Error or Canceled there is nothing to serve; fix the build and redeploy. If a good build exists but is not Production, promote it.

Expected: the Deployments tab shows a Ready build marked Production.

5. If the domain shows as assigned but the error persists, check whose project it is assigned to. A domain can only serve one project; assigned to a different project or team in the same account, it 404s on yours.

Expected: the domain sits on the project you are testing, in the team you are testing.

Variant phrasings

404 notfound code deploymentnot_found

The full error page text as one search string. Same diagnosis and same fix: attach the domain (step 2) or promote a Ready build (step 4).

deployment not found vercel

The plain-words version of the same failure. If Vercel answered the request, the code on the page is DEPLOYMENTNOTFOUND even when the person searching does not quote it.

vercel domain 404 after adding custom domain

Adding DNS records is only half of the setup: until the domain is also added under Settings, Domains on the project, Vercel has nowhere to route it and returns this code.

Root cause

Vercel routes each hostname to one specific deployment. If the domain was never added to the project, was removed, or the deployment the URL pointed at was deleted, the edge has nowhere to send the request and returns DEPLOYMENTNOTFOUND. Redeploying does not attach a domain, which is why people get stuck in a redeploy loop.

Edge cases

• Domain assigned but still 404ing: DNS may still be propagating (up to 24 hours), or the domain is assigned to a different project or team.
• Deployment Protection is on: deployment URLs ask for a Vercel login by design. That is not this error; use the production domain instead.
• The default project.vercel.app name is taken by someone else: pick another project name so the default slug is free.

Tool compatibility

Vercel, all plans (Hobby, Pro, Enterprise), for both vercel.app domains and custom domains. Dashboard steps are the same on every plan.

Related skills

• Vercel Blob client upload: Access denied, provide a valid token - a different Vercel failure, after the deployment itself loads: https://vectle.com/skills/sklk8NXBSuuEqWele64_QODA
• Diagnose timeouts for AI routes deployed on Vercel: https://vectle.com/skills/skl_jxLAo75dHb9lR1SE4WsruQ

Provenance

Built from real deployment writeups documenting this exact failure, linked in the evidence.

Multiple real deployment writeups document this exact failure. One project manual records the troubleshooting entry verbatim: Error: 404: NOT_FOUND Code: DEPLOYMENT_NOT_FOUND, with the diagnosis that DNS is pointing at Vercel fine but Vercel does not know which project to display, and the verified fix: go to the Vercel Dashboard, open the project, Settings -> Domains, type the domain and click Add, then refresh. A second writeup adds the key distinction: read the code on the 404 page, because NOTFOUND means a deployment is serving but the route has no match, while DEPLOYMENTNOTFOUND means no deployment is attached to the hostname at all, fixed by attaching the domain or promoting the right build to Production. Full threads: https://github.com/bgillis99-pixel/final-125111am/blob/HEAD/DEPLOYMENTMANUAL.md and https://github.com/sakshamfit/restaurant/blob/HEAD/DEPLOY.md