Error Codes
If an error occurs in API calling, no result is returned. Identify the error cause based on the error codes of each API. If an error occurs in API calling, an HTTP status code is returned. The response body contains the specific error code and information.
{
"error_id": "CS.11004",
"error_name": "JOB_NAME_EXIST",
"error_cause": "This job name is already existed",
"error_suggestion": "Please choose a new job name",
"error_time": 1538016904593
} The following table describes the common error codes.
| Error Code | Status Code | Description | Solution |
|---|---|---|---|
| CS.10001 | 400 | An internal error occurred on the service. | Submit a service ticket for troubleshooting or try again later. |
| CS.10002 | 400 | The requested resource is forbidden. | Refer to the Cloud Stream Service API Reference. |
| CS.10003 | 400 | The requested API is not supported. A complete API contains the API domain name, path, HTTP method, query parameters, request body, request header parameters, path parameters, response status code, response header, response body, and more. | Select a correct API and try again, or check whether the API specifications are met. For details, see the Cloud Stream Service API Reference. |
| CS.10004 | 400 | The JSON format of the request body is incorrect. | Refer to the Cloud Stream Service API Reference or JSON format specifications. |
| CS.10005 | 400 | You have no permission to perform this request. | Confirm your permissions. |
| CS.10006 | 400 | The project ID in the URL is different from that in the IAM token. | Check whether the project ID in the IAM token is correct. |
| CS.10007 | 400 | The IAM token has expired. | Log in again and re-call this API. |
| CS.10008 | 400 | There is no token in the request header. | Add X-Auth-Token to the request header. |
| CS.10009 | 400 | The account is frozen because the account balance is less than 0. | Top up the account. |
| CS.10010 | 400 | The user ID or project ID does not exist in the IAM token. | Contact technical support. |
| CS.10014 | 400 | Permission denied or insufficient balance. | Grant the permission to the account or top up the account. |
| CS.10015 | 400 | IAM request failed. | Try again later. |
| CS.10016 | 400 | Real-time authentication is not performed before resource creation. | Complete the real-name authentication. |
| CS.11001 | 400 | The maximum length of a SQL statement is 10,000 bytes. | Specify a shorter SQL statement. |
| CS.11002 | 400 | The OBS bucket must be provided if the checkpoint function or OBS is enabled. | Configure checkpoint_obs_bucket in the request. |
| CS.11003 | 400 | A maximum of 100 jobs in the Draft status are allowed. | Delete unused jobs in the Draft status. |
| CS.11004 | 400 | The job name exists. | Select a new job name. |
| CS.11005 | 400 | Failed to submit the stream SQL job. | Submit a service ticket for troubleshooting. |
| CS.11006 | 400 | The maximum length of a job name is 57 bytes. | Specify a shorter job name. |
| CS.11007 | 400 | The job name cannot be left blank. | Enter a job name. |
| CS.11008 | 400 | Invalid checkpoint_interval setting. | As specified in the Cloud Stream Service API Reference, if checkpointEnabled is set to true, checkpoint_interval cannot be left blank. |
| CS.11009 | 400 | Invalid checkpoint_mode setting. | As specified in the Cloud Stream Service API Reference, if checkpointEnabled is set to true, checkpoint_mode cannot be left blank. |
| CS.11010 | 400 | The obs_bucket parameter is not specified. | As specified in the Cloud Stream Service API Reference, if checkpointEnabled is set to true, obs_bucket cannot be left blank. |
| CS.11011 | 400 | Invalid obs_bucket setting | As specified in the Cloud Stream Service API Reference, if log_enabled is set to true, obs_bucket cannot be left blank. |
| CS.11012 | 400 | The SPU quantity for a job is beyond the value range. | Set the SPU quantity to a value ranging from 1 to 400. |
| CS.11013 | 400 | The maximum number of parallel jobs is beyond the value range. | Set the maximum number of parallel jobs to a value ranging from 1 to 50. |
| CS.11014 | 400 | The maximum length of a job description is 512 bytes. | Specify a shorter job description. |
| CS.11015 | 400 | A job name consists of letters, digits, underscores (_), and hyphens (-). | Provide a valid job name. |
| CS.11016 | 400 | Permission to access an OBS bucket has not been granted to CS. | Grant CS the permission to access this OBS bucket. |
| CS.11017 | 400 | The uploaded file is not a JAR file. | Upload a JAR file. |
| CS.11018 | 400 | The main class name of a JAR job includes a maximum of 512 bytes. | Specify a shorter main class name. |
| CS.11019 | 400 | The main class arguments of a job include a maximum of 1,024 bytes. | Specify shorter main class arguments. |
| CS.11020 | 400 | The job main class name includes spaces. | Delete the spaces in the job main class name. |
| CS.11021 | 400 | The JAR file does not exist. | Select an available JAR file. |
| CS.11022 | 400 | Parallelism of a job cannot exceed four times of the SPU quantity for the compute unit. | Set Parallelism to be not greater than four times of the SPU quantity for the compute unit. |
| CS.11023 | 400 | No edge computing group is specified. | Specify the edge_group_id parameter. |
| CS.11024 | 400 | The job type and the running mode mismatch. | Use the correct running mode. |
| CS.11025 | 400 | Invalid SPU quantity for the management unit. | Enter a valid number of SPUs. Ensure that the number of SPUs for management units is not less than 1 or not greater than the total number of SPUs minus 1 but does not exceed 4. |
| CS.11026 | 400 | Parameters executor_spu and executor_number must be specified for Spark streaming JAR jobs. Total number of SPUs = executor_spu x executor_number + manager_spu | Provide a valid value. |
| CS.11027 | 400 | The value of Executor_spu ranges from 1 to 4. | Provide a valid value. |
| CS.11028 | 400 | The value of Executor_num ranges from 1 to 100. | Provide a valid value. |
| CS.11029 | 400 | The parameter must be specified. | Configure the corresponding parameter. |
| CS.11030 | 400 | The configuration file does not exist. | Select a valid configuration file. |
| CS.11031 | 400 | The size of the uploaded local file cannot exceed 8 MB. | Upload files to OBS or upload a file not greater than 8 MB. |
| CS.11032 | 400 | The SMN topic does not exist. | Select an existing SMN topic. |
| CS.11035 | 400 | UDFs cannot be used in the shared cluster. | Select an exclusive cluster. |
| CS.11036 | 400 | The idle state retention time ranges from 1s to 60s. | Provide a valid value. |
| CS.11037 | 400 | Failed to aggregate job logs. | Try again later. |
| CS.11038 | 400 | The log dump function is disabled. | Enable the function on the job editing page. |
| CS.11039 | 400 | Invalid dirty data policy. | Provide a valid dirty data policy. |
| CS.11040 | 400 | Failed to aggregate user data. | Try again later. |
| CS.11041 | 400 | Failed to upload user data. | Try again later. |
| CS.11098 | 400 | Failed to obtain the APIG address of the job. | Try again later. |
| CS.12001 | 400 | Invalid job ID. The job ID must be a digit greater than 0. | Provide a valid job ID, which can be obtained from the CS job list. |
| CS.12002 | 400 | Failed to update the Stream SQL statements. | Check the system and try again. |
| CS.12003 | 400 | Jobs in the Running or Submitting status cannot be updated. | Wait until the job is completed and try again. |
| CS.12004 | 400 | The job does not exist. | Check the reason or create a job. |
| CS.12005 | 400 | The job cannot be updated. | Check why the job cannot be updated. |
| CS.12006 | 400 | The job name already exists. | Try a new job name. |
| CS.13001 | 400 | Insufficient quota. | Contact the administrator to adjust the quota. |
| CS.13002 | 400 | Insufficient SPUs. | Contact the administrator to adjust the cluster quota. |
| CS.13003 | 400 | The snapshot or logging function has been enabled, but no OBS bucket is selected. | Select an OBS bucket or disable the snapshot or logging function. |
| CS.13004 | 400 | Permission to access an OBS bucket has not been granted to CS. | Grant CS the permission to access the OBS bucket or disable the snapshot or logging function. |
| CS.13005 | 400 | Incorrect SQL syntax. | View error details in the SQL editor and modify the statements. |
| CS.13006 | 400 | The job is running or is not allowed to run. | Check the job status. |
| CS.13007 | 400 | The job ID does not exist. | Provide an available job ID, which can be obtained from the CS job list. |
| CS.13008 | 400 | An exclusive cluster not in the Running status is selected for running jobs. | Provide an available cluster ID, which can be obtained from the CS cluster list. |
| CS.13009 | 400 | User-defined jobs cannot run on the shared cluster. | Select an exclusive cluster. |
| CS.13010 | 400 | Exceptions occur during job running. | Check job logs. |
| CS.13011 | 400 | The user does not have the permission to use the cluster. | Select an available cluster. |
| CS.13012 | 400 | Incorrect job type. | Enter a correct JAR job type. |
| CS.13013 | 400 | The JAR file does not exist. | Upload a valid JAR file. |
| CS.13014 | 400 | A job with Kafka as the source or sink stream cannot run on the shared cluster. | Select an exclusive cluster. |
| CS.13015 | 400 | Incorrect type setting for the source or sink stream. | Enter a correct source/sink stream type. |
| CS.13016 | 400 | A job with {0} as the source or sink stream cannot run on the shared cluster. | Select an exclusive cluster. |
| CS.13017 | 400 | The job savepoint does not exist. | Create a job savepoint first. You can choose whether to create the savepoint when stopping a job. |
| CS.13018 | 400 | No JAR file is contained in the path specified by jar_url. | Ensure that at least a valid JAR file is contained in the path specified by jar_url. |
| CS.13019 | 400 | The main_class parameter must be specified when there are multiple JAR files in the path specified by jar_url. | Specify the main_class parameter when there are multiple JAR files in the path specified by jar_url. |
| CS.14001 | 400 | The job execution graph does not exist. | Try again later. |
| CS.15001 | 400 | The job ID does not exist. | Provide an available job ID, which can be obtained from the CS job list. |
| CS.15002 | 400 | You are not allowed to stop the job in the current status. | Refer to the Cloud Stream Service API Reference. |
| CS.16001 | 400 | The job ID does not exist. | Provide an available job ID, which can be obtained from the CS job list. |
| CS.17001 | 400 | The job ID does not exist. | Provide an available job ID, which can be obtained from the CS job list. |
| CS.18001 | 400 | The maximum length of a SQL statement in a template is 10,000 bytes. | Specify a shorter SQL statement. |
| CS.18002 | 400 | The template name already exists. | Select a new template name. |
| CS.18003 | 400 | A maximum of 100 templates are allowed. | Delete unused templates. |
| CS.18004 | 400 | The JSON format of the request body is incorrect. | Refer to the Cloud Stream Service API Reference. |
| CS.18005 | 400 | The template does not exist. | Specify an existing template ID. |
| CS.18006 | 400 | The template name cannot be left blank. | Specify a template name. |
| CS.18007 | 400 | A template name consists of letters, digits, underscores (_), and hyphens (-). | Provide a valid template name. |
| CS.18008 | 400 | The template description includes a maximum of 512 bytes. | Specify a shorter template description. |
| CS.18009 | 400 | The template name includes a maximum of 64 bytes. | Specify a shorter template name. |
| CS.19001 | 400 | The JSON format of the request body is incorrect. | Refer to the Cloud Stream Service API Reference or JSON format specifications. |
| CS.19002 | 400 | Failed to authorize OBS bucket {Bucket name}. | Submit a service ticket for troubleshooting. |
| CS.19003 | 400 | The bucket to be authorized does not exist. | Use a correct OBS bucket. |
| CS.19004 | 400 | No OBS bucket name in the request body. | Add the OBS bucket name in JSON array format to the request body. |
| CS.19005 | 400 | The request contains names of authorized OBS buckets. | Filter out names of authorized OBS buckets. |
| CS.19006 | 400 | An agency named cloud_stream_agency already exists but is not authorized to CS. | Modify the agency configuration or delete the agency on the IAM console. |
| CS.19007 | 400 | No agency is created for CS. | Create an agency. |
| CS.19008 | 400 | Failed to create an agency. | Submit a service ticket for troubleshooting. |
| CS.19009 | 400 | Failed to grant permissions to the agency. | Submit a service ticket for troubleshooting. |
| CS.19010 | 400 | Insufficient permissions granted to the agency. | Proceed to the authorization. |
| CS.19011 | 400 | Insufficient agency quota. | Go to the IAM console and delete unused agencies. |
| CS.20001 | 400 | Failed to create a cluster. | Try again later or submit a service ticket for troubleshooting. |
| CS.20002 | 400 | The JSON format of the request body is incorrect. | Refer to the Cloud Stream Service API Reference or JSON format specifications. |
| CS.20003 | 400 | A maximum of 400 SPUs can be configured for a cluster. | Reduce the maximum number of SPUs configured for a cluster to 400 or less. |
| CS.20004 | 400 | The total number of available SPUs for all clusters is {0}. | Reduce the cluster quota to {0} or less. |
| CS.20005 | 400 | The cluster does not exist. | Specify an existing cluster ID. |
| CS.20006 | 400 | The cluster name exists. | Select a new cluster name. |
| CS.20007 | 400 | The number {0} of SPUs that have been used by a cluster exceeds the maximum SPU quota. | Specify a value greater than {0} for the maximum SPU quota of the cluster. |
| CS.20008 | 400 | The cluster name cannot be left blank. | Specify a cluster name. |
| CS.20009 | 400 | The maximum length of a cluster name is 100 bytes. | Specify a shorter cluster name. |
| CS.20010 | 400 | The maximum length of a cluster description is 512 bytes. | Specify a shorter cluster description. |
| CS.20011 | 400 | A cluster name consists of letters, digits, underscores (_), and hyphens (-). | Provide a valid cluster name. |
| CS.20012 | 400 | The SPU quota must be greater than 0. | Provide an SPU quota greater than 0. |
| CS.20013 | 400 | The maximum SPU quota is 1,000. | Reduce the SPU quota to 1,000 or less. |
| CS.20014 | 400 | Insufficient resources. | New cluster resources are being prepared. Try again later. |
| CS.20015 | 400 | Clusters not in the Running status cannot be modified. | Modify cluster information when it is running. |
| CS.20016 | 400 | Failed to stop the cluster due to arrears. | Check, on CS Backend, whether it has stopped. |
| CS.20017 | 400 | Failed to restore the frozen cluster. | Manually restore the cluster. |
| CS.20021 | 400 | Check the cluster billing mode and status. | Only pay-per-use clusters in the Stopped or Stopped due to arrears status can be restarted. |
| CS.20022 | 400 | Incorrect cluster network configuration. | Modify the network configuration. |
| CS.20023 | 400 | The manager_node_spu parameter setting is incorrect in the request body. | Use a valid manager_node_spu setting in the request body. |
| CS.20024 | 400 | Nodes of the specification corresponding to manager_node_spu in the request body have been sold out. | Use a valid manager_node_spu setting in the request body. |
| CS.20025 | 400 | Compute nodes of the corresponding specifications have been sold out. | Submit a service ticket. |
| CS.20026 | 400 | This operation cannot be performed on clusters that are not in the Running status. | Check the cluster. |
| CS.20027 | 400 | The cluster billed on a yearly/monthly basis cannot be manually deleted. | Cancel subscription. |
| CS.20028 | 400 | The cluster billed on a yearly/monthly basis cannot be manually stopped. | Cancel subscription. |
| CS.20029 | 400 | The maximum resource quota of a cluster billed on a yearly/monthly basis cannot be modified. | Apply for quota change. |
| CS.21001 | 400 | Failed to query cluster information. | Try again later or submit a service ticket for troubleshooting. |
| CS.21011 | 400 | Failed to delete a cluster. | Submit a service ticket for troubleshooting. |
| CS.21031 | 400 | Failed to obtain the cluster list due to the incorrect limit parameter setting. | Set the limit parameter to a value greater than 0. |
| CS.21091 | 400 | The number of used SPUs {0} exceeds the maximum SPU quota. | Specify a value greater than {0} for the maximum SPU quota. |
| CS.21092 | 400 | The user ID does not exist. | Provide a valid user ID. |
| CS.21095 | 400 | Failed to obtain the user quota because the invalid limit parameter setting. | Set the limit parameter to a value greater than 0. |
| CS.21999 | 400 | Failed to update the SPU quota. | Check the failure cause. |
| CS.22001 | 400 | Incorrect IP address or domain name format. | Provide a correct IP address and domain name. |
| CS.22002 | 400 | The IP address or domain name already exists. | Ensure that the domain name is unique and the IP address and domain name cannot be the same as those of the cluster node. |
| CS.22003 | 400 | The domain name ID does not exist. | Provide a correct domain name ID. |
| CS.22004 | 400 | Incorrect hosts file format. | Ensure that each line in the file is in the "ip hostname" format. If an IP address corresponds to multiple domain names, the line can be in the "ip hostname1 hostname2" format. |
| CS.22005 | 400 | The hosts file is empty. | Provide a correct file. |
| CS.22006 | 400 | The size of the hosts file exceeds the upper limit. | Ensure that the size of the hosts file is not greater than 8 MB. |
| CS.22007 | 400 | The number of IP-domain mappings exceeds 1,000. | Delete unused IP-domain mappings. |
| CS.22101 | 400 | The VPC ID does not exist. | Provide a correct VPC ID. |
| CS.22102 | 400 | A conflict occurs during the creation of a VPC peering connection. | Provide valid parameters. |
| CS.22103 | 400 | The ID of the VPC peering connection does not exist. | Provide a valid VPC peering connection ID. |
| CS.22104 | 400 | The destination parameter in the request body is not set. | Set the destination parameter in the request body. |
| CS.22105 | 400 | The VPC peering connection is not in the ACTIVE state. | Check the status of the VPC peering connection. If it is in the Awaiting Acceptance state, accept the request and try again. |
| CS.22106 | 400 | A conflict occurs when a route is created due to invalid parameters. | Provide valid parameters. |
| CS.22107 | 400 | The route ID does not exist. | Provide a correct route ID. |
| CS.22108 | 400 | The name parameter is missing in the request body. | Add the name parameter to the request body. |
| CS.23003 | 400 | Failed to query the job list due to the incorrect root_job_id parameter setting. | Set the root_job_id parameter to a value greater than 0. |
| CS.24001 | 400 | A maximum of 50 audit logs can be queried. | Query 50 or less audit logs. |
| CS.24002 | 400 | The resource type of the audit log is job, template, or cluster. | Use the correct resource type. |
| CS.24003 | 400 | No tracker is found. | Enable CTS. |
| CS.24010 | 400 | Failed to query audit logs. | Try again later or submit a service ticket for troubleshooting. |
| CS.25001 | 400 | Failed to query CS overview statistics. | Try again later. |
| CS.25003 | 400 | Failed to query historical billing information. | Try again later. |
| CS.26500 | 400 | An internal error occurred on the service. | Submit a service ticket for troubleshooting or try again later. |
Last Article: Status Code
Next Article: Obtaining a Project ID
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.