Error Code
Last Updated：2020-07-20
Error Code Format
For any error in access to API, the error code and error information are returned to the user to identify and solve the problem. When an error occurs in the request, the detailed error message is returned via Response Body and in the following format:
| Parameter Name | Type | Description |
|---|---|---|
| code | String | Indicates the specific error type. |
| message | String | Detailed description about the error. |
| requestId | String | RequestId that caused the error. |
For example:
{
"code":"IllegalRequestUrl",
"message":"The requested url belongs to domain which is not under acceleration",
"requestId":" 81d0b05f-5ad4-1f22-8068-d5c9de60a1d7"
}Public Error Code
| Error Code | Error Message | HTTP States Code | Description |
|---|---|---|---|
| AccessDenied | Access denied. | 403 Forbidden | You have no permission to access the resources. |
| InappropriateJSON | The JSON you provided was well-formed and valid, but not appropriate for this operation. | 400 Bad Request | The JSON format in the request is correct but does not meet the requirements in semantics. For example, a required item is missing, or the value type does not match. For the consideration of compatibility, all unrecognized items are directly ignored, and this error is not returned. |
| InternalError | We encountered an internal error. Please try again. | 500Internal Server Error | All other undefined errors. It is not used when there are other types of errors (including common and service customized errors) corresponded definitely. |
| InvalidAccessKeyId | The Access Key ID you provided does not exist in our records. | 403 Forbidden | The Access Key ID does not exist. |
| InvalidHTTPAuthHeader | The HTTP authorization header is invalid. Consult the service documentation for details. | 400 Bad Request | The Authorization header field format is an error. |
| InvalidHTTPRequest | There was an error in the body of your HTTP request. | 400 Bad Request | The HTTP body format is an error. For example, it does not conform to the specified Encoding, etc. |
| InvalidURI | Could not parse the specified URI. | 400 Bad Request | The URI form is incorrect. For example, the keywords defined by some services are not matched. For the problem of ID mismatch, more specific error codes are defined, such as NoSuchKey. |
| MalformedJSON | The JSON you provided was not well-formed. | 400 Bad Request | The JSON format is illegal. |
| InvalidVersion | The API version specified was invalid. | 404 Not Found | The URI version number is illegal. |
| OptInRequired | A subscription for the service is required. | 403 Forbidden | No corresponding service is activated. |
| PreconditionFailed | The specified If-Match header doesn’t match the ETag header. | 412 Precondition Failed | For more information, please see Etag. |
| RequestExpired | Request has expired. Timestamp date is XXX. | 400 Bad Request | Request timeout. XXX is changed to an x-bce-date value. If there is only Date in the request, you need to change Date to datetime. |
| IdempotentParameterMismatch | The request uses the same client token as a previous, but non-identical request. | 403 Forbidden | API parameters corresponding to clientToken are different. |
| SignatureDoesNotMatch | The request signature we calculated does not match the signature you provided. Check your Secret Access Key and signing method. Consult the service documentation for details. | 400 Bad Request | The signature attached to the Authorization header field does not match that verified by the server. |
BMR Error Code
| Error Code | Error Message | HTTP States Code | Description |
|---|---|---|---|
| ClusterNotFound | The requested cluster does not exist. Please double confirm your clusterId or the existence of the cluster. | 404 | The accessed cluster does not exist. Please double confirm if the specified cluster ID is correct or if the specified cluster exists. |
| ClusterOverLimit | The maximum number of your Running or Waiting clusters is 5. | 403 | A single user keeps 5 active (running or waiting) clusters at maximum. |
| InappropriateJSON | The JSON provided is well-formed and valid, but not appropriate for this operation. | 400 | The JSON format in the request is correct but does not meet the requirements in semantics. For example, a required parameter is missing, or the parameter type does not match. All unrecognized parameters are directly ignored, and this error is not returned. |
| InsufficientBalance | Insufficient balance, please refill your account. | 403 | Refill the account because of insufficient balance. |
| InternalError | We encountered an internal error. Please try again or contact us. | 500 | All other undefined errors. |
| InvalidArguments | The arguments of step properties can not be parsed correctly. | 400 | An error occurs in parsing the step parameters. Please double confirm if the step parameters entered are correct. |
| InvalidBosPath | The BOS path provided may be malformed or incorrect. | 400 | The BOS path is illegal. Please double confirm if the BOS file on which the request relies exists and enter the correct path. |
| InvalidInstanceGroupType | Instance group type should be Master or Core. | 400 | Instance Group Types include Master, Core or Task. |
| InvalidInstanceType | The instance type specified is invalid. | 400 | The instance type is not recognized. Please see the Instance Specifications to enter the instance type. |
| InvalidStepType | The step type specified is invalid. | 400 | The step type is not recognized. Please see the codes in Step Types to enter the type. |
| InvalidVersion | The API version specified is invalid. | 404 | The URI version number is illegal. The current value is 1. |
| MalformedJSON | The JSON provided is not well-formed. | 400 | The JSON format is illegal. |
| MissingProperties | One or more required fields are missing in step properties. | 400 | The required information is missing in step properties. Please specify the required fields as per the step type. |
| OperationDenied | The request could not be fulfilled. | 403 | The conditions for fulfilling the request are not met. |
| StepNotFound | The requested step does not exist. Please double confirm your stepId or the existence of the step. | 404 | The accessed step does not exist. Please double confirm if the specified step ID is correct or if the specified step exists. |
| StepOverLimit | The maximum number of steps in one cluster is 256. | 403 | The total number of steps submitted in a single cluster is not more than 256. Try to operate more steps via interactive access. |
| ValidationError | The request fails to satisfy the constraints specified by BMR service. | 400 | The request does not conform to BMR service specifications. Please check if the request path, request header field, parameters, and message body format are satisfactory. |
| Invalid_RootDisk_Type | The specified type system disk does not exist. | 400 | The system disk of this type does not exist. Please check your configuration. Please see the codes in Cloud Disk Types to enter the type |
| Invalid_CdsDataDisk_Type | The specified type data disk does not exist. | 400 | The data disk of this type does not exist. Please check your configuration. Please see the codes in Cloud Disk Types to enter the type |