400

10240002

The number of queried queues exceeds the upper limit.

400

10240004

The tag name is invalid.

400

10240005

The project ID format is invalid.

400

10240007

The name contains invalid characters.

400

10240009

The message body is not in JSON format or contains invalid characters.

400

10240010

The description contains invalid characters.

400

10240011

The name length must be 1 to 64 characters.

400

10240012

The name length must be 1 to 32 characters.

400

10240013

The description length must not exceed 160 characters.

400

10240014

The number of consumable messages exceeds the maximum limit.

400

10240015

The queue ID format is invalid.

400

10240016

The group ID format is invalid.

400

10240017

The queue already exists.

400

10240018

The consumer group already exists.

400

10240019

The number of consumer groups exceeds the upper limit.

400

10240020

The quota is insufficient.

400

10240021

The value of time_wait is not within the value range of 1–60.

400

10240022

The value of max Consume Count must be within the range of 1–100.

400

10240027

The value of retention_hours must be an integer in the range of 1–72.

400

10240028

Non-kafka queues do not support retention_hours.

400

10240032

The queue is being created.

401

10240101

Invalid token.

401

10240102

Expired token.

401

10240103

Missing token.

401

10240104

The project ID and token do not match.

403

10240304

Change the quota of a queue or consumer group to a value smaller than the used quota.

403

10240306

The tenant has been frozen. You cannot perform operations on DMS.

403

10240308

The queue quota must be within the range of 1–20.

403

10240309

Access denied. You cannot perform operations on DMS.

403

10240310

A tenant has read-only permissions and cannot perform operations on DMS.

403

10240311

This role does not have the permissions to perform this operation.

403

10240312

The tenant is restricted and cannot perform operations on DMS.

404

10240401

The queue ID is incorrect or not found.

404

10240405

The consumer group ID is incorrect or not found.

404

10240406

The URL or endpoint does not exist.

500

10250002

Internal service error.

500

10250003

Internal service error.

500

10250004

Internal service error.

500

10250005

Internal communication error.

500

10250006

Internal service error.

400

10540001

The message body contains invalid fields.

400

10540003

Message ack status must be either 'success' or 'fail'. It should not be '{status}'.

400

10540004

Request error: The queue or group name does not match the handler.

400

10540010

The request format is incorrect: {error description}.

400

10540011

The message size is {message size}, larger than the size limit {max allowed size}.

400

10540012

The message body is not in JSON format or contains invalid characters.

400

10540014

The URL contains invalid parameters.

400

10540202

The request format is incorrect: {error description}.

400

10542204

Failed to consume messages due to {desc}.

400

10542205

Failed to obtain the consumption instance because the handler does not exist. This may be because the consumer instance is released 1 minute after the message is consumed. As a result, the consumer instance fails to be obtained from the handler.

This error code is returned in the following scenarios:

• The handler of another consumption instance is submitted.
• The message consumption is acknowledged more than 1 minute after the message is consumed.
• A dead letter message consumption API is used to acknowledge the consumption of normal messages.
• A normal message consumption API is used to acknowledge the consumption of dead letter messages.

400

10542206

The value of ack_wait must be within the range of 15–300.

400

10542209

The handler does not exist because the handler fails to be parsed, the message consumption times out, or the message consumption is repeatedly acknowledged.

This error code is returned in the following scenarios:

• A wrong handler is submitted after the message is consumed.
• The message is not consumed and a fake handler is used to acknowledge the message consumption.
• The message consumption is acknowledged more than 30s after the message is consumed.
• A used handler is used to repeatedly acknowledge message consumption within 30s after the message is consumed.

Due to performance concerns, the system timeout timing mechanism is not very precise, and the system performs periodic timeout detection instead of real-time detection.

400

10542214

The request format is incorrect: {error description}.

404

10240407

The request is too frequent. Flow control is being performed. Please try again later.

404

10540401

The queue name does not exist.

500

10550035

tag_type must be either or or and.

400

111400002

The project ID format is invalid.

400

111400004

The request body is empty.

400

111400005

The message body is not in JSON format or contains invalid characters.

400

111400007

Unsupported type.

400

111400008

Unsupported version.

400

111400009

Invalid product_id.

400

111400010

Invalid instance name. The name must be 4 to 64 characters long. Only letters, digits, underscores (_), and hyphens (-) are allowed.

400

111400011

The instance description can contain a maximum of 1024 characters.

400

111400012

The password does not meet the complexity requirements.

An instance password must:

• Be a string consisting of 8 to 32 characters.
• Contain at least two of the following character types:
  • Lowercase letters
  • Uppercase letters
  • Digits
  • Special characters `~!@#$%^&*()-_=+\|[{}];:',<.>/?

400

111400013

vpc_id in the request is empty.

400

111400014

security_group_id in the request is empty.

400

111400015

Invalid username. A username must be 4 to 64 characters long and consist of only letters, digits, and hyphens (-).

400

111400016

subnet_id in the request is empty.

400

111400018

This subnet must exist in the VPC.

400

111400019

The password does not meet the complexity requirements.

400

111400020

DHCP must be enabled for this subnet.

400

111400026

This operation is not allowed due to the instance status.

400

111400037

The instanceParams parameter in the request contains invalid characters or is not in JSON format.

400

111400038

The periodNum parameter in the request must be an integer.

400

111400042

The AZ does not exist.

400

111400045

The instance is not frozen and cannot be unfrozen.

400

111400046

This security group does not exist.

400

111400048

Invalid security group rules. Ensure that rules with the protocol being ANY are configured for both the inbound and outbound directions.

400

111400060

This instance name already exists.

400

111400061

Invalid instance ID format.

400

111400062

Invalid request parameter. The status of an instance to be queried must be a value listed in Table 1.

400

111400063

Invalid configuration parameter {0}.

400

111400064

The action parameter in the request must be delete or restart.

400

111400065

The instances parameter in the request is empty.

400

111400066

Invalid configuration parameter {0}.

400

111400067

The available_zones parameter in the request must be an array that contains only one AZ ID.

400

111400068

The VPC does not exist.

400

111400080

Incorrect instance password.

400

111400081

Duplicate instance name.

400

111400099

The following instances in the Creating, Starting, Stopping, or Restarting state cannot be deleted: {}

400

111400100

The instances array can contain a maximum of 50 instance IDs.

400

111400101

The name of a Kafka topic must be 4 to 64 characters long and start with a letter. Only letters, digits, underscores (_), and hyphens (-) are allowed.

400

111400102

The number of partitions created for a Kafka topic must be within the range of 1–20.

400

111400103

The number of replicas created for a Kafka topic must be within the range of 1–20.

400

111400105

The message retention period of a Kafka topic must be within the range of 1–168.

400

111400106

Invalid maintenance time window.

400

111400800

• Duplicate topic name.
• Invalid request. You can create, delete, or query a topic only for a Kafka instance.
• Invalid parameter. Error information varies by scenario.

401

111401001

Invalid token.

401

111401003

The token is missing.

401

111401004

The project ID and token do not match.

403

111403002

A tenant has the read-only permission and cannot perform operations on DMS.

403

111403003

This role does not have the permissions to perform this operation.

404

111404001

The requested URL does not exist.

404

111404022

This instance does not exist.

404

111404024

Connector does not exist.

404

111404026

The dumping task does not exist.

404

111404027

Connector already exists.

404

111404029

The dumping task quota has been reached.

405

111405001

This request method is not allowed.

400

111400500

Invalid disk space.

400

111400125

Invalid SPEC_CODE.

400

111400124

The maximum number of disk expansion times has been reached.

500

111500000

Internal service error.

500

111500006

Internal service error.

500

111500017

Internal service error.

500

111500023

Internal service error.

500

111500024

Internal service error.

500

111500025

Internal service error.

500

111500041

Internal service error.

500

111500051

Internal service error.

500

111500052

Internal service error.

500

111500053

Internal service error.

500

111500054

Internal service error.

500

111500070

Internal service error.

500

111500071

Internal service error.

500

111500094

Internal service error.

500

111500106

Internal service error.