Deleting Messages in Batch

Last updated: 2019-07-05 14:26:37

1. API Description

This API (BatchDeleteMessage) is used to delete a batch of messages (currently you can delete up to 16 messages at a time) that have already been consumed. The consumer needs to use the ReceiptHandle (obtained after the last consume operation) as parameter to locate the messages to be deleted. You can only execute this operation before NextVisibleTime. Messages will return to Active status after NextVisibleTime and ReceiptHandle will become invalid, causing deletion operation to fail. In this case, you will need to re-consume the messages and acquire ReceiptHandle again. Under concurrent consuming scenario, if a message is deleted by one of the consumers, the other consumers will no longer be able to obtain the deleted message.

Domain for public network API

Domain for private network API

At any time (including alpha test), any downstream traffic generated when using public network domain will incur traffic fee. It is strongly recommended that users on Tencent Cloud use private network domain, as it will not incur any traffic fee.

  • The "region" should be replaced by a specific region: gz (Guangzhou), sh (Shanghai), bj (Beijing). The "region" value in the common parameter should be kept consistent with that in the domain. In case of inconsistency, the one in the domain should prevail. The request should be sent to the region specified by the domain.
  • Requests for accessing via public network domain support both HTTP and HTTPS. Requests for accessing via private network only support HTTP.
  • Some of the input parameters are optional, so the default values are not required.
  • All output parameters will be returned to the user when the request is successful; otherwise, at least code, message, and requestId will be returned.

2. Input Parameters

The following request parameter list only provides API request parameters. For other parameters, refer to Common Request Parameters.

Parameter Name Required Type Description
queueName Yes String Queue name. This is unique under the same account in one region. The name of queue is a string with no more than 64 characters. It must start with letter, and the rest may contain letters, numbers and dashes (-).
receiptHandle.n Yes String Receipt handle returned when consuming message the last time. To make it more convenient for users, "n" may start from either 0 or 1, but is must be continuous. For example, if you delete two messages, they can be (receiptHandle.0,receiptHandle.1) or (receiptHandle.1, receiptHandle.2).

3. Output Parameters

Parameter Name Type Description
code Int 0: Succeed, 4420: Maximum qps limit has been reached, 4440: Queue does not exist, 6010: Failed to delete some of the messages, 6020: Failed to delete any of the messages. For the meanings of other returned values, please refer to Error Codes.
message String Error message.
requestId String ID of the request generated by server. When there is an internal error on the server, users can submit this ID to backend to locate the problem.
errorList Array List of errors regarding failed deletion operations. Each element contains the error and reason for why a message could not be deleted.

errorList is defined as follows:

Parameter Name Type Description
code Int 0: Succeeded, others: Error. For detailed errors, please refer to the table below.
message String Error message.
receiptHandle String Receipt handle of the message that was not successfully deleted.
Error Code Module Error Code Error Message Description
6010 10150 delete message partially failed Failed to delete some of the messages in the batch. An error message will be provided for each of the messages that was not successfully deleted. Failed deletions are likely caused by invalid receipt handles.
4430 10260 receipt handle is invalid Receipt handle is invalid. Refer to Delete Messages for the reasons for why handles become invalid.
6020 10290 batch delete message failed Failed to batch delete messages.
4000 10470 receiptHandle error receiptHandle error. receiptHandle is a string

Note: The error codes listed in the above table are specific to the API. If the error code you are looking for is not here, you may find it in the Common Error Codes.

4. Example


 &<Common request parameters>


When all are successfully deleted

"code" : 0,
"message" : "",

When part of the messages are not successfully deleted

"code" : 6010,
"message" : "delete message partially failed",
"code" : 4430,
"message" : "invalid receiptHandle",