Error Codes
Quickly resolve Vercel issues with our detailed Error Codes guide. Find specific solutions and insights for common Vercel errors, enhancing your development experience. Explore now to streamline your troubleshooting process.When developing your application with Vercel, you may encounter a variety of errors. They can reflect issues that happen with external providers such as domain services or internal problems at the level of your application's deployment or your usage of platform features.
The following list of error codes is categorized based on tags. You can use the tag filter below to find errors that are relevant to your use case, or use the search bar to find a specific error code.
For general error handling guidance, that covers dashboard related errors, see General Errors.
BODY_NOT_A_STRING_FROM_FUNCTION
The
BODY_NOT_A_STRING_FROM_FUNCTION
error occurs when a Serverless Function does not return a string as its body. Functions must return a string body to ensure that they can be correctly processed and executed.502FunctionEDGE_FUNCTION_INVOCATION_FAILED
The
EDGE_FUNCTION_INVOCATION_FAILED
error occurs when there is an issue with the Edge Function being invoked on the Edge Network. This error can be caused by a variety of issues, including unhandled exceptions, timeouts, or malformed requests.500FunctionINTERNAL_EDGE_FUNCTION_INVOCATION_FAILED
The
INTERNAL_EDGE_FUNCTION_INVOCATION_FAILED
error occurs when there is an issue with the Edge Function being invoked on the Edge Network. This error can be caused by a variety of issues, including unhandled exceptions, timeouts, or malformed requests.500InternalINTERNAL_EDGE_FUNCTION_INVOCATION_TIMEOUT
The
INTERNAL_EDGE_FUNCTION_INVOCATION_TIMEOUT
error occurs when an Edge Function takes longer than the allowed execution time to complete. This can be caused by long-running processes within the function or external dependencies that fail to respond in a timely manner.504InternalEDGE_FUNCTION_INVOCATION_TIMEOUT
The
EDGE_FUNCTION_INVOCATION_TIMEOUT
error occurs when an Edge Function takes longer than the allowed execution time to complete. This can be caused by long-running processes within the function or external dependencies that fail to respond in a timely manner.504Common errorFunctionFUNCTION_INVOCATION_FAILED
The
FUNCTION_INVOCATION_FAILED
error occurs when a function invocation fails. This could be due to an error within the function itself, or an issue with the environment in which the function is running.500Common errorFunctionFUNCTION_INVOCATION_TIMEOUT
The
FUNCTION_INVOCATION_TIMEOUT
error occurs when a function invocation takes longer than the allowed execution time. This could be due to an error within the function itself, a slow network call, or an issue with the environment in which the function is running.504Common errorFunctionFUNCTION_PAYLOAD_TOO_LARGE
The
FUNCTION_PAYLOAD_TOO_LARGE
error occurs when the payload sent to a function exceeds the maximum allowed size. This typically happens when the data sent in the request body to a serverless function is larger than the server can process.413FunctionFUNCTION_RESPONSE_PAYLOAD_TOO_LARGE
The
FUNCTION_RESPONSE_PAYLOAD_TOO_LARGE
error occurs when a function returned a response that exceeds the maximum allowed size.500FunctionFUNCTION_RATE_LIMIT
The
FUNCTION_RATE_LIMIT
error occurs when the default limit of concurrent executions for Serverless Functions has been reached, and the request triggers a new instance of the function, which results in two concurrent functions running at the same time.429FunctionINTERNAL_FUNCTION_INVOCATION_FAILED
The
INTERNAL_FUNCTION_INVOCATION_FAILED
error occurs when an internal function invocation fails. This could be due to an error within the function itself, or an issue with the environment in which the function is running.500InternalINTERNAL_FUNCTION_INVOCATION_TIMEOUT
The
INTERNAL_FUNCTION_INVOCATION_TIMEOUT
error occurs when a function invocation takes longer than the allowed execution time. This could be due to an error within the function itself, a slow network call, or an issue with the environment in which the function is running.504InternalINTERNAL_FUNCTION_NOT_FOUND
The
INTERNAL_FUNCTION_NOT_FOUND
error occurs when an attempt to invoke a function fails because the function could not be found. This could happen if the function was not properly deployed, or if there is a misconfiguration in the function's settings or environment.500InternalINTERNAL_FUNCTION_NOT_READY
The
INTERNAL_FUNCTION_NOT_READY
error occurs when an attempt is made to invoke a function before it is ready to accept requests. This might happen if the function is still being deployed, initialized, or if there is a misconfiguration preventing the function from becoming ready.500InternalNO_RESPONSE_FROM_FUNCTION
The
NO_RESPONSE_FROM_FUNCTION
error occurs when a function invocation completes without returning a response. This might happen if the function encounters an error that prevents it from responding, or if it fails to generate a response within the allowed execution time.502FunctionDEPLOYMENT_BLOCKED
The
DEPLOYMENT_BLOCKED
error occurs when a deployment is blocked due to certain conditions that prevent it from proceeding. This could happen due to various reasons such as configuration errors, account limitations, or policy violations.403DeploymentDEPLOYMENT_PAUSED
The
DEPLOYMENT_PAUSED
error occurs when a deployment is paused due to certain conditions or configurations. This might happen if there's a manual intervention required, or a specific condition is met that triggers the pause.503DeploymentDEPLOYMENT_DISABLED
The
DEPLOYMENT_DISABLED
error occurs when a deployment is disabled due to certain conditions or configurations. This might happen if there's a manual intervention required, or a specific condition is met that triggers the disabling of the deployment.402Common errorDeploymentDEPLOYMENT_NOT_FOUND
The
DEPLOYMENT_NOT_FOUND
error occurs when a request is made for a deployment that doesn't exist. This could happen if the deployment ID or URL is incorrect, or if the deployment has been deleted.404Common errorDeploymentNOT_FOUND
The
NOT_FOUND
error occurs when a requested resource could not be found. This might happen if the resource has been moved, deleted, or if there is a typo in the URL.404Common errorDeploymentDEPLOYMENT_NOT_READY_REDIRECTING
The
DEPLOYMENT_NOT_READY_REDIRECTING
error occurs when the requested deployment is not yet ready, and the request is redirected to the deployment status page.303DeploymentINTERNAL_DEPLOYMENT_FETCH_FAILED
The
INTERNAL_DEPLOYMENT_FETCH_FAILED
error occurs when the system is unable to fetch the deployment. This could happen due to network issues, misconfigurations, or other internal errors that prevent the deployment data from being retrieved.500InternalINTERNAL_UNARCHIVE_FAILED
The
INTERNAL_UNARCHIVE_FAILED
error typically occurs when the platform encounters a problem trying to extract your deployment's archive. This issue often can be related to the structure of your project or the contents within it, or the size of your deployment bundle for Serverless Functions exceeds the limit. For Serverless Functions, the maximum uncompressed size is 250 MB500InternalINFINITE_LOOP_DETECTED
The
INFINITE_LOOP_DETECTED
error occurs when an infinite loop is detected within the application. This error can occur when the application is making an infinite number of requests to itself, or when the application is making an infinite number of requests to an external API or database.508RuntimeINTERNAL_UNEXPECTED_ERROR
The
INTERNAL_UNEXPECTED_ERROR
error occurs when an unexpected and unspecified internal error happens within the system. This type of error can be due to a variety of reasons, including system faults, unhandled exceptions, or unforeseen issues in the application.500InternalDNS_HOSTNAME_EMPTY
The
DNS_HOSTNAME_EMPTY
error occurs when an empty DNS record is received as part of the DNS response while attempting to connect to a private IP from an external rewrite.502DNSDNS_HOSTNAME_NOT_FOUND
The
DNS_HOSTNAME_NOT_FOUND
error occurs when there's an NXDOMAIN error during the DNS resolution while attempting to connect to a private IP from an external rewrite. This error indicates that the domain being requested does not exist.502DNSDNS_HOSTNAME_RESOLVE_FAILED
The
DNS_HOSTNAME_RESOLVE_FAILED
error occurs when attempting to connect to a private IP from an external rewrite. This could be due to an issue with the domain name being queried, corrupted or malformed DNS responses, or network issues.502DNSDNS_HOSTNAME_RESOLVED_PRIVATE
The
DNS_HOSTNAME_RESOLVED_PRIVATE
error occurs when attempting to connect to a private IP from an external rewrite. The error indicates that the DNS hostname resolved to a private or unaccessible IP address.404DNSDNS_HOSTNAME_SERVER_ERROR
The
DNS_HOSTNAME_SERVER_ERROR
error occurs when attempting to connect to a private IP from an external rewrite. This error typically means that the DNS server was unable to fulfill the DNS request due to an internal issue or misconfiguration502DNSTOO_MANY_FORKS
The
TOO_MANY_FORKS
error occurs when too many forks are generated while processing the request. This usually happens when matching too many conditional routes, which could lead to a loop or excessive resource usage.502RoutingTOO_MANY_FILESYSTEM_CHECKS
The
TOO_MANY_FILESYSTEM_CHECKS
error occurs when there are excessive filesystem checks while processing a request. This could happen during the routing process, especially when using rewrites, redirects, or any other configuration that requires checking the filesystem repeatedly.502RoutingINTERNAL_ROUTER_CANNOT_PARSE_PATH
The Edge Network has failed to parse application-specified URL, such as rewrite/redirection URLs.
500InternalROUTER_CANNOT_MATCH
The
ROUTER_CANNOT_MATCH
error occurs when the router is unable to match the requested route to any of the known patterns. This could happen due to a misconfiguration in the routing setup or an erroneous request path.502RoutingROUTER_EXTERNAL_TARGET_CONNECTION_ERROR
The
ROUTER_EXTERNAL_TARGET_CONNECTION_ERROR
error occurs when there is a connection error while routing to an external target. This could happen due to network issues, incorrect routing configuration, or the external target being unreachable.502RoutingROUTER_EXTERNAL_TARGET_ERROR
The
ROUTER_EXTERNAL_TARGET_ERROR
error occurs when there is an error while routing to an external target. This could happen due to incorrect routing configuration, an erroneous response from the external target, or other issues affecting the routing process.502RoutingROUTER_TOO_MANY_HAS_SELECTIONS
The
ROUTER_TOO_MANY_HAS_SELECTIONS
error occurs when the router encounters too many selections while processing the request. This could happen due to misconfiguration or a complex routing setup that exceeds the router's capabilities.502RoutingROUTER_EXTERNAL_TARGET_HANDSHAKE_ERROR
The
ROUTER_EXTERNAL_TARGET_HANDSHAKE_ERROR
error occurs when a connection cannot be successfully established with an external target. This error may result from issues during the SSL handshake process or due to a timeout502RoutingINVALID_REQUEST_METHOD
The
INVALID_REQUEST_METHOD
error occurs when a request is made with a method that is either invalid or not supported by the server. This error typically happens when trying to use an HTTP method that the endpoint does not accept or recognize.405Common errorRequestMALFORMED_REQUEST_HEADER
The
MALFORMED_REQUEST_HEADER
error signifies that a request made to the server includes a header that is incorrectly formatted or contains invalid data. This could be due to syntax errors, incorrect header field names, or incompatible header values.400RequestREQUEST_HEADER_TOO_LARGE
The
REQUEST_HEADER_TOO_LARGE
error occurs when the size of the request headers in Edge Functions and Middleware exceeds the allowed limits. Specifically, individual request headers must not exceed 16 KB, and the combined size of all headers, including the header names, must not exceed 32 KB.431RequestINTERNAL_STATIC_REQUEST_FAILED
The
INTERNAL_STATIC_REQUEST_FAILED
error is encountered when a request for a static file within the project cannot be completed. This can happen due to issues with the existence, deployment, or path of the static files.502InternalRESOURCE_NOT_FOUND
The
RESOURCE_NOT_FOUND
error indicates that a requested resource is not available or cannot be found. This error typically arises when a request is made for a resource that either does not exist or is currently inaccessible.404RequestRANGE_END_NOT_VALID
The
RANGE_END_NOT_VALID
error occurs when the end value of the Range header in a request is invalid. This header is used to request a specific portion of a resource from the server, which is useful for operations like resuming downloads or streaming media.416RequestRANGE_GROUP_NOT_VALID
The
RANGE_GROUP_NOT_VALID
error occurs when the group value of the Range header in a request is invalid. This header is used to request a specific portion of a resource from the server, and the group value can be used to specify multiple ranges or a set of subranges.416RequestRANGE_MISSING_UNIT
The
RANGE_MISSING_UNIT
error occurs when the unit identifier of the Range header in a request is missing. The Range header is used to request a specific portion of a resource from the server, and the unit identifier indicates the unit in which the range is specified, such as bytes.416Common errorRequestRANGE_START_NOT_VALID
The
RANGE_START_NOT_VALID
error occurs when the start value of the Range header in a request is invalid. The Range header is used to request a specific portion of a resource from the server, and the start value should be a valid integer indicating the beginning of the requested range.416RequestRANGE_UNIT_NOT_SUPPORTED
The
RANGE_UNIT_NOT_SUPPORTED
error occurs when the unit identifier of the Range header in a request is not supported by the server. The Range header is used to request a specific portion of a resource from the server, and the unit identifier indicates the unit in which the range is specified, such as bytes.416RequestTOO_MANY_RANGES
The
TOO_MANY_RANGES
error occurs when too many ranges have been specified in the Range header of a request. The Range header is used to request specific portions of a resource from the server, and specifying too many ranges can lead to an excessive load on the server.416RequestURL_TOO_LONG
The
URL_TOO_LONG
error occurs when the URL of the request exceeds the maximum length allowed by the server or by the HTTP specification. Long URLs can be a result of long query strings, lengthy path segments, or an excessive number of path segments.414RequestFALLBACK_BODY_TOO_LARGE
The
FALLBACK_BODY_TOO_LARGE
error indicates that the size of the fallback body exceeds the maximum cache limit. This error typically occurs in prerendered pages when the response body of a fallback page is larger than the cache can accommodate. Notably, if the fallback exceeds 10MB, it cannot be cached.502CacheINTERNAL_CACHE_ERROR
An unexpected error happened when Edge Network is fetching data from the Vercel cache.
500InternalINTERNAL_CACHE_KEY_TOO_LONG
The Edge Network is failing to fetch from the internal cache due to a cache key being too long. This error can be caused by a request URL that is too long.
500InternalINTERNAL_CACHE_LOCK_FULL
An unexpected error happened when Edge Network is accessing internal cache.
500InternalINTERNAL_CACHE_LOCK_TIMEOUT
An unexpected error happened when Edge Network is accessing internal cache.
500InternalINTERNAL_MISSING_RESPONSE_FROM_CACHE
The
INTERNAL_MISSING_RESPONSE_FROM_CACHE
error occurs when a response expected from the cache is not found. This may happen during deployment or build processes and can be caused by issues with the cache state or configuration.500Internal
Was this helpful?