Error Codes
If API calling fails, no result data is returned. You can locate the error cause according to the error code of each API. When the API calling fails, HTTP status code 4xx or 5xx is returned. The returned message body contains the specific error code and error information. If you fail to locate the cause of an error, contact and provide the error code so that we can help you solve the problem as soon as possible.
The following is an example of an error response:
{ "errors": [ { "error_code": "DLV.1000", "error_msg": "Screen number exceed quota." } ] }
Status Code |
Error Code |
Error Message |
Solution |
---|---|---|---|
400 |
DLV.1000 |
Insufficient screen quota. |
Delete the screen and try again. |
400 |
DLV.1001 |
The screen name exists. Use another name. |
Check whether the name of the screen is the same as that of the existing screen. |
400 |
DLV.1003 |
Processing failed. |
Contact the service administrator. |
400 |
DLV.1004 |
Errors occurred during your operation. |
Contact the service administrator. |
400 |
DLV.1005 |
Invalid screen name. |
Correct the screen name and try again. |
500 |
DLV.1006 |
Invalid screen configuration. |
Correct the request parameter settings and try again. |
400 |
DLV.1007 |
The screen does not exist. |
Check the screen ID and ensure it is correct. |
400 |
DLV.1008 |
The screen is already shared. |
Check whether the screen has been published. |
400 |
DLV.1009 |
The screen is not shared. |
Publish the screen and try again. |
400 |
DLV.1010 |
The component configuration is null. |
Correct the request parameter settings and try again. |
400 |
DLV.1011 |
Invalid template ID. |
Correct the template ID and try again. |
400 |
DLV.1012 |
Invalid screen ID. |
Correct the screen ID and try again. |
400 |
DLV.1013 |
Invalid snapshot ID. |
Correct the snapshot ID and try again. |
400 |
DLV.1014 |
The data source name exists. Use another name. |
Change the name and try again. |
400 |
DLV.1015 |
The data source name does not exist. |
Correct the parameter settings and try again. |
400 |
DLV.1016 |
The parameter information is incomplete. |
Correct the parameter settings and try again. |
400 |
DLV.1017 |
The data source type is not supported. |
Change the supported data source type and try again. |
400 |
DLV.1018 |
The component does not exist. |
Correct the parameter settings and try again. |
400 |
DLV.1019 |
Incorrect subordinate relationship. |
Correct the parameter settings and try again. |
400 |
DLV.1020 |
The template ID cannot be empty. |
Correct the parameter settings and try again. |
400 |
DLV.1021 |
Insufficient snapshot quota. |
Ensure that the number of snapshots does not exceed the threshold and try again. |
500 |
DLV.1022 |
The comList of screenConfig mismatches the components in the component list. |
Correct the parameter settings and try again. |
400 |
DLV.1023 |
Failed to obtain the cluster. |
Contact the service administrator. |
400 |
DLV.1024 |
The image does not exist. |
Correct the parameter settings and try again. |
400 |
DLV.1025 |
Failed to create the data connection. |
Contact the service administrator. |
400 |
DLV.1026 |
Invalid template name. |
Correct the parameter settings and try again. |
400 |
DLV.1027 |
The template is already published. |
Do not publish the template again. |
400 |
DLV.1028 |
The template is not published. |
Publish the template and try again. |
400 |
DLV.1029 |
The template does not exist. |
Correct the parameter settings and try again. |
400 |
DLV.1030 |
The template status is null. |
Contact the service administrator. |
400 |
DLV.1031 |
Failed to submit the job. |
Contact the service administrator. |
400 |
DLV.1032 |
Failed to obtain the job status. |
Contact the service administrator. |
400 |
DLV.1033 |
Failed to obtain the job result. |
Contact the service administrator. |
400 |
DLV.1034 |
Failed to connect to DLI. |
Contact the service administrator. |
400 |
DLV.1035 |
Failed to obtain the job result because the schema or row is empty. |
Contact the service administrator. |
400 |
DLV.1036 |
Failed to obtain the queue. |
Contact the service administrator. |
400 |
DLV.1037 |
Failed to obtain the database. |
Contact the service administrator. |
400 |
DLV.1038 |
Failed to upload the image. |
Correct the parameter settings and try again. |
400 |
DLV.1039 |
The file type is incorrect. |
Correct the parameter settings and try again. |
400 |
DLV.1040 |
The file size exceeds the upper limit. |
Try a smaller file. |
400 |
DLV.1041 |
Invalid data source name. |
Correct the parameter settings and try again. |
400 |
DLV.6311 |
Failed to obtain the MRS cluster information. |
Contact the service administrator. |
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