Error Codes for Service 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 .
Status Code |
Error Code |
Error Message |
Description |
Solution |
---|---|---|---|---|
400 |
GES.8000 |
Incorrect parameter format. |
Incorrect parameter format. |
Check whether the request body is the same as that described in the document. |
400 |
GES.8001 |
Failed to query graph statistics. |
Failed to query graph statistics. |
|
500 |
GES.8002 |
Graph statistics query error. |
Graph statistics query error. |
|
400 |
GES.8005 |
Incorrect parameter. |
Incorrect parameter. |
|
400 |
GES.8006 |
Invalid resource access. |
Invalid resource access. |
Check whether the project ID in the URL is correct. |
400 |
GES.8007 |
Invalid token. |
Invalid token. |
Check whether the token is correct. |
400 |
GES.8008 |
An error occurs in the underlying authentication system. |
An error occurs in the underlying authentication system. |
Try again later or contact technical personnel. |
400 |
GES.8011 |
Failed to export a graph. |
Failed to export a graph. |
|
400 |
GES.8012 |
Failed to clear a graph. |
Failed to clear a graph. |
|
400 |
GES.8013 |
Failed to incrementally import data to the graph. |
Failed to incrementally import data to the graph. |
|
400 |
GES.8020 |
The current user does not have permission. |
The current user does not have the required permission for granular permission control. |
|
400 |
GES.8101 |
Invalid filter criteria for edge queries. |
Invalid filter criteria for edge queries. |
Check whether format of the filter criteria for edge queries is correct. |
400 |
GES.8102 |
Invalid label for edge filtering queries. |
Invalid label for edge filtering queries. |
Check whether the labels are in the correct JSON format. |
400 |
GES.8103 |
Both the condition and label of edge filtering queries are empty. |
Both the condition and label of edge filtering queries are empty. |
The condition and label of edge filtering queries cannot be both empty. |
400 |
GES.8104 |
Invalid edge filtering query sequence. |
Invalid edge filtering query sequence. |
Check whether the edge filtering query sequence is valid. |
400 |
GES.8105 |
Failed to query edges that meet filter criteria. |
Failed to query edges that meet filter criteria. |
|
400 |
GES.8106 |
The source vertex or target vertex in the edge details is empty. |
The source vertex or target vertex in the edge details is empty. |
Ensure that the source vertex or target vertex in the edge details cannot be empty. |
400 |
GES.8107 |
Failed to query edge details. |
Failed to query edge details. |
|
500 |
GES.8108 |
Edge details query error. |
Edge details query error. |
Try again later or contact technical personnel. |
400 |
GES.8109 |
Invalid edge filtering query operator. |
Invalid edge filtering query operator. |
Ensure that the values of edge filtering query operators are in, out, both, and edge. |
400 |
GES.8110 |
Parameter edges cannot be left blank. |
Parameter edges cannot be left blank. |
Check whether the value of edges in the batch edge query request body is empty. |
400 |
GES.8201 |
Invalid label for vertex filtering queries. |
Invalid label for vertex filtering queries. |
Check whether the labels are in the correct JSON format. |
400 |
GES.8202 |
Invalid filter criteria for vertex queries. |
Invalid filter criteria for vertex queries. |
|
400 |
GES.8203 |
Both the condition and label of vertex filtering queries are empty. |
Both the condition and label of vertex filtering queries are empty. |
Ensure that the condition and label of vertex filtering queries are not both empty. |
400 |
GES.8204 |
Failed to query vertices that meet filter criteria. |
Failed to query vertices that meet filter criteria. |
|
400 |
GES.8205 |
Invalid vertex filtering query sequence. |
Invalid vertex filtering query sequence. |
In the vertex filtering query API, orderValue must be set to incr or decr. |
400 |
GES.8206 |
Both vertexid and vertextids exist. |
Both vertexid and vertextids exist. |
vertexid and vertextids cannot coexist. |
400 |
GES.8207 |
Both vertexid and vertextids are empty. |
Both vertexid and vertextids are empty. |
The vertexid or vertextids parameter is empty. |
400 |
GES.8208 |
Incorrect vertextids format. |
Incorrect vertextids format. |
Check whether vertextids is a JSON array. |
400 |
GES.8209 |
Failed to query vertex details. |
Failed to query vertex details. |
Check whether the graph name exists. |
500 |
GES.8210 |
Vertex details query error. |
Vertex details query error. |
Try again later or contact technical personnel. |
400 |
GES.8211 |
Invalid vertex filtering query operator. |
Invalid vertex filtering query operator. |
Ensure that values of vertex filtering query operators are inV, outV, bothV, and vertex. |
400 |
GES.8212 |
Failed to delete the vertex label. |
Failed to delete the vertex label. |
Check whether the label exists. |
400 |
GES.8213 |
Failed to add the vertex label. |
Failed to add the vertex label. |
Check whether the label exists. |
400 |
GES.8214 |
Parameter vertices cannot be left blank. |
Parameter vertices cannot be left blank. |
Check whether the value of vertices in the batch vertex query request body is empty. |
400 |
GES.8220 |
Failed to update the vertex properties. |
Failed to update the vertex properties. |
|
400 |
GES.8221 |
Failed to update the edge properties. |
Failed to update the edge properties. |
|
400 |
GES.8301 |
Failed to query a job. |
Failed to query a job. |
|
500 |
GES.8302 |
Job query error. |
Job query error. |
Try again later or contact technical personnel. |
400 |
GES.8303 |
Failed to terminate a job. |
Failed to terminate a job. |
|
500 |
GES.8304 |
Job termination error. |
Job termination error. |
Try again later or contact technical personnel. |
400 |
GES.8401 |
The algorithm or graph name cannot be empty. |
The algorithm or graph name cannot be empty. |
Ensure that the algorithm or graph name in not empty. |
400 |
GES.8402 |
Failed to run the algorithm. |
Failed to run the algorithm. |
|
500 |
GES.8403 |
Algorithm running error. |
Algorithm running error. |
Try again later or contact technical personnel. |
400 |
GES.8404 |
Invalid algorithm running format. |
Invalid algorithm running format. |
|
400 |
GES.8501 |
The Gremlin command is not supported. |
The Gremlin command is not supported. |
Replace the unsupported Gremlin statements: tryNext, explain, and tree. |
400 |
GES.8502 |
Failed to find the Gremlin configuration file. |
Failed to find the Gremlin configuration file. |
Try again later or contact technical personnel. |
400 |
GES.8503 |
Gremlin query failed. |
Gremlin query failed. |
|
500 |
GES.8504 |
Gremlin query error. |
Gremlin query error. |
Try again later or contact technical personnel. |
400 |
GES.8505 |
The Gremlin query statement does not contain the command field. |
The Gremlin query statement does not contain the command field. |
Ensure that the Gremlin query statement does not contain the command field. |
400 |
GES.8506 |
The size of the Gremlin query request statements exceeds the upper limit. |
The size of the Gremlin query request statements exceeds the upper limit. |
The current limit is 64 MB. |
500 |
GES.8601 |
Gremlin service unavailable. |
Gremlin service unavailable. |
Try again later or contact technical personnel. |
500 |
GES.8602 |
Engine service unavailable. |
Engine service unavailable. |
Try again later or contact technical personnel. |
400 |
GES.8603 |
Failed to create an index |
Failed to create an index |
|
400 |
GES.8604 |
Failed to delete an index |
Failed to delete an index |
|
400 |
GES.8605 |
Failed to query an index |
Failed to query an index |
|
400 |
GES.8609 |
The request body for querying path details is invalid. |
The request body for querying path details is invalid. |
|
400 |
GES.8610 |
The path parameter of the request body for querying path details is invalid. |
The path parameter of the request body for querying path details is invalid. |
|
400 |
GES.8611 |
Failed to query path details. |
Failed to query path details. |
|
400 |
GES.8612 |
The operation of querying path details is not supported. |
The operation of querying path details is not supported. |
|
400 |
GES.8801 |
Failed to add a label to metadata. |
Failed to add a label to metadata. |
|
400 |
GES.8803 |
Failed to query the metadata. |
Failed to query the metadata. |
|
500 |
GES.8804 |
Metadata query error. |
Metadata query error. |
Try again later or contact technical personnel. |
400 |
GES.8806 |
K-Hop query with filter criteria failed. |
K-Hop query with filter criteria failed. |
|
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot