You can call this operation to resend a specific dead-letter message by setting the message ID so that the message can be re-consumed by the consumer.
This operation revives a dead-letter message and enables the message to be consumed by the consumer again.
The maximum number of retries for a dead-letter message has been reached. If the message fails to be consumed again after being resent, a message with the same message ID will be added to the dead-letter queue. You can view the result on the Dead-Letter Queue page in the console or by calling the O&M API. You can identify the number of consumption failures after resending a message according to the number of messages with the same message ID.
A dead-letter message fails to be consumed after executing the retry logic. This often indicates that the consumption logic may have an error. Therefore, check the reasons for multiple times of consumption failure, and then call this operation to resend the message.
RocketMQ does not manage the resending status of dead-letter messages. If a message is successfully consumed after being resent, the message will not be removed from the dead-letter queue. You need to manually manage and determine whether a message needs to be resent to avoid repeated consumption due to meaningless resending.
|PreventCache||Long||Yes||The parameter that is used for CSRF verification, which can be set to the current system time. Unit: ms|
|InstanceId||String||Yes||The ID of the instance for the message that you want to query.|
|MsgId||String||Yes||The ID of the message that you want to query (message ID).|
|GroupId||String||Yes||The consumer group ID of the message that you want to query.|
|RequestId||String||A common parameter. Each request has a unique ID.|
|HelpUrl||String||A help link.|
||The ID of the message that fails to be sent (message ID).|
For more information about sample codes, see API sample code and endpoints.