Data Development Error Codes
The error response is in the following format:
{
"error_code":"DLF.0100",
"error_msg":"The job not found"
}
Table 1 describes the error codes.
Status Code |
Error Code |
Error Message |
Description |
Solution |
---|---|---|---|---|
400 |
DLF.0100 |
The job does not exist. |
The Job does not exist. |
Ensure that the job exists. |
400 |
DLF.0101 |
The job quota has reached the upper limit. |
The job quota has reached the upper limit. |
Apply for a higher quota. |
400 |
DLF.0102 |
The job name has been used by another job. |
The job name has been used by another job. |
Try another name. |
400 |
DLF.0136 |
This API can be called only for batch jobs. |
This API can be called only for batch jobs. |
Check the job. |
400 |
DLF.0137 |
The job instance does not exist. |
The job instance does not exist. |
Ensure that the job instance exists. |
400 |
DLF.0201 |
The script fails to be created. |
The script fails to be created. |
Check the script. |
400 |
DLF.0202 |
The script name has been used by another script. |
The script name has been used by another script. |
Try another name. |
400 |
DLF.0203 |
The script fails to be modified. |
The script fails to be modified. |
Check the script. |
400 |
DLF.0802 |
The specified parameter is not configured. |
The specified parameter is not configured. |
Check the parameter. |
400 |
DLF.0803 |
The OBS path is invalid. |
The OBS path is invalid. |
Check the OBS path. |
400 |
DLF.0810 |
The queried task does not exist. |
The queried task does not exist. |
Check that the task exists. |
400 |
DLF.0815 |
The OBS file fails to be accessed. |
The OBS file fails to be accessed. |
Check the OBS file. |
400 |
DLF.1006 |
The job node is empty. |
The job node is empty. |
Check the node. |
400 |
DLF.1242 |
The OBS bucket does not exist. |
The OBS bucket does not exist. |
Ensure that the OBS bucket exists. |
400 |
DLF.2014 |
The job object type is invalid. |
The job type is invalid. |
Check the job type. |
400 |
DLF.3004 |
The job name cannot be left blank. |
The job name cannot be left blank. |
Check the job name. |
400 |
DLF.3018 |
The job name is invalid. |
The job name is invalid. |
Check the job name. |
400 |
DLF.3025 |
The job scheduling parameter is invalid. |
The job scheduling parameter is invalid. |
Check the job scheduling parameter. |
400 |
DLF.3050 |
The job description is invalid. |
The job description is invalid. |
Check the job description. |
400 |
DLF.6201 |
The script does not exist. |
The script does not exist. |
Ensure that the script exists. |
400 |
DLF.6205 |
The script execution instance does not exist. |
The script execution instance does not exist. |
Check that the script execution instance exists. |
400 |
DLF.6241 |
The resource to be queried does not exist. |
The resource to be queried does not exist. |
Ensure that the resource exists. |
400 |
DLF.6247 |
The script type is not specified. |
The script type is not specified. |
Check the script. |
400 |
DLF.6253 |
The script quota has reached the upper limit. |
The script quota has reached the upper limit. |
Apply for a higher quota. |
400 |
DLF.6258 |
The directory contains data that cannot be deleted. |
The directory contains data that cannot be deleted. |
Delete the data in the directory first. |
400 |
DLF.6259 |
A resource with the same name already exists in the directory. |
A resource with the same name already exists in the directory. |
Try another name. |
400 |
DLF.6263 |
The resource type is invalid. |
The resource type is invalid. |
Check the resource type. |
400 |
DLF.6264 |
The OBS path of the resource file is invalid. |
The OBS path of the resource file is invalid. |
Check the OBS path. |
400 |
DLF.6265 |
The resource description is invalid. |
The resource description is invalid. |
Check the resource description. |
400 |
DLF.6271 |
Each user can create only one DLI connection. |
Each user can create only one DLI connection. |
Check the DLI data connection. |
400 |
DLF.6309 |
The connection name has been used by another connection. |
The connection name has been used by another connection. |
Try another connection name. |
400 |
DLF.6322 |
The data connection does not exist. |
The data connection does not exist. |
Check that the data connection exists. |
400 |
DLF.6323 |
The connection type cannot be modified. |
The connection type cannot be modified. |
Check the parameter type. |
400 |
DLF.6416 |
The cluster has been occupied by another connection. |
The cluster has been occupied by another connection. |
Check the cluster. |
400 |
DLF.6418 |
Either the DWS cluster name or the access address and port number of the cluster must be configured. |
Either the DWS cluster name or the access address and port number of the cluster must be configured. |
Check the DWS cluster name or the access address and port of the cluster. |
400 |
DLF.6423 |
An exception occurs when the agent is creating a job. |
An exception occurred during the agent job creation. |
Try again later or check whether the agent status is normal. |
400 |
DLF.6888 |
Invalid account permissions. |
Invalid account permissions. |
Check the account permissions. |
400 |
DLF.21123 |
The single node job type cannot be empty. |
The single-node job type cannot be empty. |
Select the single-node job type. |
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