vercel
Vercel Error Codes
Error codes shown by Vercel when a deployment, route, or Vercel Function fails. Each code pairs an HTTP status with a stable identifier such as FUNCTION_INVOCATION_TIMEOUT, surfaced on the error page and in runtime logs.
11 codes
· All codes 11 codes
- DEPLOYMENT_BLOCKED Deployment Blocked Access to the deployment was blocked, typically by Vercel's firewall or DDoS mitigation after detecting abusive or malicious traffic, or because the deployment violates Vercel's terms of service. Returned with HTTP 403; review the project's firewall and deployment protection settings if this affects legitimate traffic.
- DEPLOYMENT_NOT_FOUND Deployment Not Found The requested deployment ID or preview URL doesn't correspond to an existing deployment, typically because it was mistyped or the deployment was deleted. Returned with HTTP 404; verify the URL in the Vercel dashboard.
- DEPLOYMENT_PAUSED Deployment Paused The project has been paused, so requests to its production deployment are rejected. This usually follows a plan downgrade, a reached spend limit, or manual action by the project owner. Returned with HTTP 503; unpause the project from the Vercel dashboard.
- DNS_HOSTNAME_NOT_FOUND DNS Hostname Not Found DNS resolution for the requested hostname returned NXDOMAIN, meaning the domain does not exist. Returned with HTTP 502; verify the domain is registered and that its DNS records are configured correctly.
- FUNCTION_INVOCATION_FAILED Function Invocation Failed A Vercel Function threw an unhandled exception or crashed while processing the request. Returned with HTTP 500; check the function's runtime logs in the Vercel dashboard for the underlying stack trace.
- FUNCTION_INVOCATION_TIMEOUT Function Invocation Timeout A Vercel Function did not finish within its configured maximum duration. Common causes are a slow upstream API or database call, or an unhandled promise that never resolves. Returned with HTTP 504; check the function's duration limit for the current plan and add timeouts around external calls.
- FUNCTION_PAYLOAD_TOO_LARGE Function Payload Too Large The request body or response body of a Vercel Function exceeded the 4.5 MB limit. Returned with HTTP 413; stream large payloads directly to storage instead of through the function, or split the request.
- NOT_FOUND Not Found The requested path doesn't match any page, static asset, or Vercel Function in the deployment. Returned with HTTP 404; check the deployed output for the expected route and confirm the build included it.
- RESOURCE_NOT_FOUND Resource Not Found A platform-level resource referenced by the request, such as a project, team, or environment variable scope, could not be found. Returned with HTTP 404; confirm the resource still exists and that the request targets the correct team or project.
- ROUTER_CANNOT_MATCH Router Cannot Match Vercel's edge router could not match the incoming request to any configured route, redirect, or rewrite pattern. Returned with HTTP 502; check vercel.json and the framework's routing configuration for conflicting or malformed rules.
- TOO_MANY_FILESYSTEM_CHECKS Too Many Filesystem Checks The router performed too many filesystem lookups while trying to resolve the request path, usually caused by a very large number of rewrite rules or a deeply recursive routing configuration. Returned with HTTP 502; simplify the rewrites in vercel.json or the framework's routing config.