Error Codes

Updated on 2022-02-22 GMT+08:00

View PDF

The error response is in the following format:

{

"error_code":"DLF.1001",

"error_msg":"The job not found"

}

Table 1 describes the error codes.

**Table 1** Error codes
Error Code	Error Message
DLF.0100	The job does not exist.
DLF.0101	The job quota has reached the upper limit.
DLF.0102	The job name has been used by another job.
DLF.0136	This API can be called only for batch jobs.
DLF.0137	The job instance does not exist.
DLF.0201	The script fails to be created.
DLF.0202	The script name has been used by another script.
DLF.0203	The script fails to be modified.
DLF.0802	The specified parameter is not configured.
DLF.0803	The OBS path is invalid.
DLF.0810	The queried task does not exist.
DLF.0815	The OBS file fails to be accessed.
DLF.1006	The job node is empty.
DLF.1242	The OBS bucket does not exist.
DLF.3004	The job name cannot be left blank.
DLF.3018	The job name is invalid.
DLF.3025	The job scheduling parameter is invalid.
DLF.3050	The job description is invalid.
DLF.6201	The script does not exist.
DLF.6205	The script execution instance does not exist.
DLF.6241	The resource to be queried does not exist.
DLF.6247	The script type is not specified.
DLF.6253	The script quota has reached the upper limit.
DLF.6258	The directory contains data that cannot be deleted.
DLF.6259	A resource with the same name already exists in the directory.
DLF.6263	The resource type is invalid.
DLF.6264	The OBS path of the resource file is invalid.
DLF.6265	The resource description is invalid.
DLF.6271	Each user can create only one DLI connection.
DLF.6309	The connection name has been used by another connection.
DLF.6322	The data connection does not exist.
DLF.6323	The connection type cannot be modified.
DLF.6416	The cluster has been occupied by another connection.
DLF.6418	Either the DWS cluster name or the access address and port number of the cluster must be configured.