Vercel 404 DEPLOYMENT_NOT_FOUND

What it means in plain English

Vercel says DEPLOYMENT_NOT_FOUND occurs when a request is made for a deployment that doesn't exist. The response is 404 DEPLOYMENT_NOT_FOUND: Not Found.

Vercel names two ways this happens: the deployment ID or URL is incorrect, or the deployment has been deleted.

A 404 on a page refresh inside a working site is a different problem. See Vercel 404 on page refresh.

Likely causes

• The deployment URL has a typo or an incorrect path.
• The deployment ID is wrong.
• The deployment was deleted.
• You do not have permission to access the deployment.

How to fix it, step by step

1. Check the deployment URL. Vercel says to make sure it is correct and has no typos or incorrect paths.
2. Check that the deployment exists and has not been deleted.
3. If the deployment exists, review its deployment logs for anything that made it unavailable.
4. Verify that you have the permissions needed to access the deployment.
5. Vercel also links its community post on debugging 404 errors.

How to check it worked

• The URL returns the site instead of 404 DEPLOYMENT_NOT_FOUND.

Sources

• https://vercel.com/docs/errors/deployment_not_found (opens in a new tab)