Error Codes for Management Plane APIs

If an error occurs in API calling, no result is returned. Identify the cause of error based on the error codes of each API. If an error occurs in API calling, HTTP status code 4xx or 5xx is returned. The response body contains the specific error code and information. If you are unable to identify the cause of an error, contact technical personnel and provide the error code so that we can help you solve the problem as soon as possible.

If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided in .

Parent topic: Error Codes

Previous topic: Error Codes

Next topic: Error Codes for Service Plane APIs

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot

Status Code	Error Code	Error Message	Description	Solution
400	GES.0001	Incorrect parameter.	Incorrect parameter.	Check whether the project ID or graph ID in the URL is correct. Check whether the request header is correct, for example, whether X-Auth-Token is correct.
400	GES.7000	The graph does not exist or has been deleted.	The graph does not exist or has been deleted.	Call the graph query API to query all graphs. Check whether the project ID or graph ID in the URL is correct.
400	GES.7001	The graph is not running.	The graph is not running.	Call the graph query API to query all graphs. View the graph list returned in the preceding step and check whether the graph status corresponding to the graph ID in the URL is 200.
400	GES.7002	The graph is being backed up.	The graph is being backed up.	Call the graph query API to query all graphs. View the graph list returned in the preceding step and check whether the graph status corresponding to the graph ID in the URL is 903.
400	GES.7003	The graph is being stopped or is stopped.	The graph is being stopped or is stopped.	Call the graph query API to query all graphs. View the graph list returned in the preceding step and check whether the graph status corresponding to the graph ID in the URL is 900 or 901.
400	GES.7004	Components at the IaaS layer are faulty.	Components at the IaaS layer are faulty.	Check whether the components at the IaaS layer, such as VPC, ECS, and OBS, are faulty.
408	GES.7005	The underlying service of the graph engine is unavailable.	The underlying service of the graph engine is unavailable.	Try again later or contact technical personnel.
400	GES.7006	An internal error occurs in the underlying service of the graph engine.	An internal error occurs in the underlying service of the graph engine.	Try again later or contact technical personnel.
400	GES.7007	The job does not exist.	The job does not exist.	Check whether the job ID in the URL is correct.
400	GES.7008	The job is stopped.	The job is stopped.	Jobs cannot be stopped repeatedly.
400	GES.7009	The job operation is not supported.	The job operation is not supported.	The job operation is not supported.
400	GES.7010	Failed to verify the schema and data files.	Failed to verify the schema and data files.	Check whether the schema file matches the edge and vertex data files.
400	GES.7011	The path or name of the schema or data file is invalid.	The path or name of the schema or data file is invalid.	Check whether the name of the scheme, vertex, or edge data file is valid. The name can contain only letters, digits, underscores (_), exclamation marks (!), hyphens (-), dot marks (.), asterisks (*), left brackets, right brackets, and slashes (/).
400	GES.7012	Failed to verify the graph name.	Failed to verify the graph name.	Check the graph name. The name contains 4 to 64 characters, starting with a letter. Only letters, digits, and underscores (_) are supported.
400	GES.7013	The graph name already exists.	The graph name already exists.	Call the graph query API to query all graphs. Query the graph list returned in the preceding step and check whether the name field in the request body already exists.
400	GES.7014	An error is reported when the metadata verification API is called.	An error is reported when the metadata verification API is called.	Check whether the value of action_id is check-schema.
400	GES.7015	The graph is not running or is stopped.	The graph is not running or is stopped.	Call the graph query API to query all graphs. View the graph list returned in the preceding step and check whether the graph corresponding to the graph ID in the URL exists or is in the 900 status.
400	GES.7016	The request body or header is invalid.	The request body or header is invalid.	Check the API reference and ensure that every configuration item in the request body and header is correctly configured.
400	GES.7017	The object does not exist. Check whether the bucket or object name is correct.	The object does not exist. Check whether the bucket or object name is correct.	Check whether the schema, vertex, and edge data files in the request body exist on OBS.
400	GES.7018	The number of graphs or edges reaches the upper limit.	The number of graphs or edges reaches the upper limit.	Call the quota query API to check whether graphs have available quotas.
400	GES.7019	The number of graph backups reaches the upper limit.	The number of graph backups reaches the upper limit.	Call the quota query API to check whether graph backups have available quotas.
400	GES.7020	The VPC does not exist.	The VPC does not exist.	Check whether the VPC ID in the request body exists.
400	GES.7021	The subnet cannot be found in the specified VPC.	The subnet cannot be found in the specified VPC.	Check whether the subnet ID in the request body exists or belongs to the preceding VPC.
400	GES.7022	The security group does not exist.	The security group does not exist.	Check whether the security group ID in the request body exists.
400	GES.7023	The graph size index is invalid.	The graph size index is invalid.	Check whether the graph size index in the request body is valid.
400	GES.7024	The graph backup does not exist or has been deleted.	The graph backup does not exist or has been deleted.	Call the backup query API to query all backups of a specified graph. Check whether the backup ID or graph ID in the URL is correct.
400	GES.7027	Failed to create an agency.	Failed to create an agency.	Assign the security administrator role to the user group to which the user belongs. If the fault persists, report the error information in errorMessage to technical personnel.
400	GES.7028	Failed to authorize an agency.	Failed to authorize an agency.	Assign the security administrator role to the user group to which the user belongs. If the fault persists, report the error information in errorMessage to technical personnel.
400	GES.7029	The agency resource exceeds the quota limit.	The agency resource exceeds the quota limit.	Check whether the agency resource reaches the quota limit on the ManageOne operation plane.
400	GES.7030	Agency query error.	Agency query error.	Check the error message for detailed information.
400	GES.7031	Invalid binding type of an EIP.	Invalid binding type of an EIP.	Confirm the EIP binding type. The value can be either of the following: bind_existing
400	GES.7032	The EIP resource exceeds the quota limit.	The EIP resource exceeds the quota limit.	Check whether the EIP resource reaches the quota limit on the VPC page.
400	GES.7033	Invalid EIP ID.	Invalid EIP ID.	If the EIP binding type is set to bind_existing, ensure that the EIP ID exists.
400	GES.7034	Resources in the current AZ have been sold out.	Resources in the current AZ have been sold out.	Switch to another AZ and try again.
400	GES.7035	Invalid region code.	Invalid region code.	Enter the correct region code.
400	GES.7036	The target version is earlier than the current version.	The target version is earlier than the current version.	A graph can only be upgraded to a later version.
400	GES.7037	The graph is not in the Stopped state.	The graph is not in the Stopped state.	Check whether the graph is in the Stopped state.
400	GES.7040	Failed to back up a graph.	Failed to back up a graph.	Failed to restore a graph from the backup you select.
400	GES.7041	Insufficient permission.	Insufficient permission.	Insufficient permission.
400	GES.7042	The graph is being created.	The graph is being created.	The graph is being created.
400	GES.7048	Invalid graph operation.	Invalid graph operation.	Check whether the value of action_id is start, stop, import-graph, export-graph, clear-graph, or upgrade.
400	GES.7049	The parameter does not exist.	The parameter does not exist.	Check whether the request body is consistent with that in the API reference. Mandatory parameters must be set.
400	GES.7050	The parameter is empty.	The parameter is empty.	Check whether the request body is consistent with that in the API reference. Mandatory parameters must be set.
400	GES.7051	Components at the IaaS layer are faulty.	Components at the IaaS layer are faulty.	If the network fluctuates, try again later. If the fault persists, obtain the log and contact customer service.
400	GES.7052	Invalid CPU architecture of the graph instance.	Invalid CPU architecture of the graph instance.	Check whether the value of arch is set to x86_64 or aarch64 when the graph is created.
400	GES.7054	The graph is being deleted or has been deleted.	The graph is being deleted or has been deleted.	This error occurs in concurrent deletion scenarios. Generally, a message indicating that the graph does not exist is displayed when you try again later.
400	GES.7056	The graph of the current flavor cannot be scaled out.	The graph of the current flavor cannot be scaled out.	Currently, ten-thousand-edge and ten-billion-edge graphs cannot be scaled out. Check whether the graph is a ten-thousand-edge or ten-billion-edge one.
400	GES.7057	Invalid graph flavor for scale-out.	Invalid graph flavor for resize.	graphSizeTypeIndex in the resize request body can be set to 2, 3, 4, or 5, indicating the ten-million-edge, hundred-million-edge, billion-edge, or ten-billion-edge graph.
400	GES.7059	The IaaS resources of the graph flavor to be scaled out are insufficient.	The IaaS resources of the graph flavor to be scaled out are insufficient.	Check whether the compute resources are sufficient. For details about the IaaS resources required by each GES flavor, see the LLD.
400	GES.7061	Failed to create the ECS because the resources are insufficient.	Failed to create the ECS because the resources are insufficient.	Check whether the compute resources are sufficient. For details about the IaaS resources required by each GES flavor, see the LLD.
400	GES.7062	Failed to create the data disk.	Failed to create the data disk.	Check the FusionStorage capacity or obtain the detailed error information from the returned errorMessage.
400	GES.7063	Failed to create the system disk.	Failed to create the system disk.	Check the FusionStorage capacity or obtain the detailed error information from the returned errorMessage.
400	GES.7064	Failed to create the ECS.	Failed to create the ECS.	See the returned errorMessage or download the microservice log on the management plane, search for the ID of failed task in the log, and contact IaaS O&M personnel.
400	GES.7065	Failed to query the image because the image does not exist.	Failed to query the image because the image does not exist.	Check whether the image ID configured on the GES management plane exists.
400	GES.7066	Failed to query the flavor.	Failed to query the flavor.	Check whether the flavor ID configured on the GES management plane exists.
400	GES.7067	Insufficient ECS quota.	Insufficient ECS quota.	Check whether the flavor ID configured on the GES management plane exists.
400	GES.7068	Invalid request parameters.	Invalid request parameters.	During graph creation, parameters in the request for calling the IaaS API are invalid. Obtain detailed information based on the returned errorMessage and contact customer service.
400	GES.7069	The metadata file is too large.	The metadata file is too large.	The metadata file on OBS or that in the request body exceeds 10 MB.
400	GES.7070	Failed to parse the metadata file.	Failed to parse the metadata file.	When creating metadata, the metadata file on OBS or in the request body does not comply with the metadata standards. Create a metadata file or request body correctly.