When an error occurs in an API request, Function Compute returns an error message. This topic provides a list of common error codes in Function Compute.

Error code format

An error code contains an HTTP status code and error details in the response body. The error details in the response body are in the following formats:

{
"errorCode" : <ErrorCode>,
"errorMessage" : <ErrorMessage>
}        

Common error codes

Among all the error messages that may be returned by Function Compute, some of them are common to most API operations, while the others are unique to specific API operations. The following table lists the common error codes in Function Compute API responses. The error codes can appear in multiple API responses. Error codes unique to an API operation are described in the corresponding API operation.

HTTP status code Error code Cause Solution
400 InvalidArgument The error message returned because invalid parameters exist. Check whether all input parameters are valid. For more information, see API specification.
400 MissingRequiredHeader The error message returned because the required request header is missing. Add the request header based on the error message.
400 LimitExceededError The error message returned because resources such as functions, triggers, and custom domain names exceed the limits. Delete unnecessary resources based on the error message. To apply for more resources, contact the Function Compute team. For contact details, see Contact us.
400 PathNotSupported The error message returned because the requested API path is invalid. Check whether the requested API path is correct. For more information, see API specification.
400 EntityTooLarge The error message returned because the input parameter value exceeds the valid value range. Enter a valid value based on the error message.
403 AccessDenied The error message returned because the account does not have permissions to perform the operation. Grant access permissions on Function Compute to the account.
403 SignatureNotMatch The error message returned because the digital signature of the request does not match with that calculated in Function Compute. Calculate the signature based on the signature rules.
403 InvalidAccessKeyID The error message returned because the AccessKey ID is invalid. Enter a valid AccessKey ID.
409 ConcurrentUpdateError The error message returned because resources such as services, functions, and triggers are being updated concurrently. Update resources sequentially to avoid data inconsistency.
429 ResourceExhausted The error message returned because the concurrency limit has been exceeded. Contact the Function Compute team to raise your concurrency limit. For contact details, see Contact us.
499 ClientClosedRequest The error message returned because the client has been disconnected. Connect to the client and adjust the disconnection time.
500 InternalServerError The error message returned because an internal server error occurred while processing your request. Contact us.
503 ResourceThrottled The error message returned because the required number of instances exceeds the limit. Contact the Function Compute team to evaluate your instance quota. For contact details, see Contact us.