Updated on 2024-05-22 GMT+08:00

Error Codes

If an error code starting with APIGW is returned after you call an API, rectify the fault according to APIG Error Codes.

Status Code

Error Code

Error Message

Description

Solution

400

CTS.0001

The IAM or OBS service is abnormal.

The IAM or OBS service is abnormal.

Contact technical support.

400

CTS.0003

The message body is empty or invalid.

The message body is empty or invalid.

Verify the body content and format.

400

CTS.0200

The number of trackers has reached the upper limit.

The number of trackers has reached the upper limit.

Delete or modify unnecessary trackers.

400

CTS.0201

A management tracker has been created.

A management tracker has been created.

Check whether a management tracker is already available.

400

CTS.0202

The value of the tracker_type parameter is incorrect.

The value of tracker_type is invalid.

Change its value to system or data.

400

CTS.0203

The value of tracker_name parameter is in an incorrect format.

The value of tracker_name is invalid.

Modify its value by referring to the parameter descriptions.

400

CTS.0204

The tracker_name parameter of a management tracker can only be set to system.

The tracker_name parameter of a management tracker can only be set to system.

Modify its value by referring to the parameter descriptions.

400

CTS.0205

The status parameter can only be set to enabled or disabled.

The status parameter can only be set to enabled or disabled.

Change its value to enabled or disabled.

400

CTS.0206

The data_bucket parameter cannot be included in the message body for a management tracker.

The data_bucket parameter cannot be included in the message body for a management tracker.

Delete the data_bucket parameter.

400

CTS.0207

The tracker_name parameter in the message body cannot be set to system for a data tracker.

The tracker_name parameter in the message body cannot be set to system for a data tracker.

Change the value of tracker_name to a value other than system.

400

CTS.0208

The tracker already exists.

The tracker already exists.

Check whether the tracker already exists.

400

CTS.0209

A type of operations on an OBS bucket can be tracked by only one tracker.

A type of operations on an OBS bucket can be tracked by only one tracker.

Change the tracker configurations.

400

CTS.0210

The OBS bucket to track cannot be empty.

The OBS bucket to be tracked cannot be empty.

Select another bucket or ensure that the bucket is not empty.

400

CTS.0211

The tracked OBS bucket does not exist.

The OBS bucket to be tracked does not exist.

Check whether bucket_name is correctly set.

400

CTS.0212

The tracked OBS bucket cannot be modified.

The tracked OBS bucket cannot be modified.

Withdraw the changes on the OBS bucket.

400

CTS.0213

The OBS bucket used for trace transfer cannot be a tracked OBS bucket.

The OBS bucket used for trace transfer cannot be a tracked OBS bucket.

Select another OBS bucket for trace transfer.

400

CTS.0215

The OBS bucket already exists.

The OBS bucket already exists.

Change the value of bucket_name.

400

CTS.0216

Failed to create a bucket.

Failed to create a bucket.

Contact technical support.

400

CTS.0217

Failed to set a lifecycle rule for the OBS bucket.

Failed to set a lifecycle rule for the OBS bucket.

Contact technical support.

400

CTS.0218

The value of file_prefix_name is in an incorrect format.

The value of file_prefix_name is invalid.

Modify its value by referring to the parameter descriptions.

400

CTS.0219

The operation type cannot be empty.

The operation type cannot be empty.

Select at least one operation type to track.

400

CTS.0220

KMS is not supported.

KMS is not supported.

Contact technical support.

400

CTS.0221

The KMS ID is empty.

The KMS ID is empty.

Check whether the KMS ID is correct.

400

CTS.0222

KMS verification failed.

KMS verification failed.

Check whether the KMS ID is correct.

400

CTS.0225

Only WRITE and/or READ operations on the OBS bucket can be tracked.

The bucket operation must be write, read, or read/write.

Check whether the input parameters are correctly set.

400

CTS.0228

The CTS service is not trusted.

CTS is not trusted.

Enable CTS as a trusted service on the Organizations console.

400

CTS.0229

The organization tracker already exists.

The organization tracker already exists.

Disable the enabled organization tracker first.

400

CTS.0231

Invalid bucket name. A bucket name must be a string of 3 to 63 characters, including only lowercase letters, digits, hyphens (-), or periods (.). It must start with a digit or a lowercase letter.

Invalid bucket name. A bucket name must contain 3 to 63 characters and start with a digit or a lowercase letter. Only lowercase letters, digits, hyphens (-), and periods (.) are allowed.

Check whether the bucket name is correct.

400

CTS.0300

Query failed.

Query failed.

Try again later or contact technical support.

403

CTS.0002

Authentication failed or you do not have the permissions required.

Authentication failed or you do not have the permissions required.

Check your permissions.

403

CTS.0013

No permission, Please check roles.

You do not have the corresponding operation permission.

Configure the permission.

404

CTS.0100

API version query is not supported in CTS.

API version query is not supported in CTS.

Contact technical support.

404

CTS.0214

The tracker does not exist.

The tracker does not exist.

Check whether the tracker has been deleted.

500

CTS.0004

Failed to write data.

Failed to write data.

Contact technical support.

500

CTS.0005

Failed to read data.

Failed to read data.

Contact technical support.