Bulk Retry DLQ messages

Retry delivery of multiple messages from the DLQ

POST /v2/dlq/retry

Bulk Retry DLQ messages

cURL

curl --request POST \
  --url https://qstash.upstash.io/v2/dlq/retry \
  --header 'Authorization: Bearer <token>'

201

{
  "cursor": "<string>",
  "responses": [
    {
      "messageId": "<string>",
      "deduplicated": true
    }
  ]
}

When DLQ messages are retried, new messages with the same body and headers are created and scheduled for delivery. The original DLQ messages are then removed from the DLQ.

You can pass all configuration headers to override the configuration of the original messages.

For example, if the retry count of the original messages is 5, you can set it to 0 for the retried messages by passing Upstash-Retries: 0 header to this request. Check out publish documentation for complete list of configuration options you can pass.

Authorizations

bearerAuthbearerAuthQuery

Authorization · string · header · required

QStash authentication token

Query Parameters

dlqIds · string[]

List of DLQ IDs to retry. If provided, other filters are ignored.

messageId · string

Filter DLQ messages by message ID

url · string

Filter DLQ messages by destination URL

topicName · string

Filter DLQ messages by URL Group name

scheduleId · string

Filter DLQ messages by schedule ID

queueName · string

Filter DLQ messages by queue name

fromDate · integer<int64>

Filter DLQ messages by starting date, in milliseconds (Unix timestamp). This is inclusive.

toDate · integer<int64>

Filter DLQ messages by ending date, in milliseconds (Unix timestamp). This is inclusive.

responseStatus · integer

Filter DLQ messages by HTTP response status code of the last delivery attempt

callerIp · string

Filter DLQ messages by IP address of the publisher

label · string[]

Filter DLQ messages by label. Supports multi-value filtering. You can pass multiple values to match messages with any of the given labels (OR logic).

Examples:

• label=my_label
• label=label_1&label=label_2

flowControlKey · string

Filter DLQ messages by Flow Control Key

Response

201

application/json

Messages retry initiated successfully

cursor · string

A cursor which you can use in subsequent requests to paginate through all messages. If no cursor is returned, you have reached the end of the messages.

responses · object[]

Show child attributes