> ## Documentation Index
> Fetch the complete documentation index at: https://upstash.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Bulk Resume Workflows from DLQ
> When a workflow run fails, it's automatically moved to the DLQ (Dead Letter Queue) where it can be analyzed and resumed.
The resume feature allows you to continue a failed workflow run from exactly where it failed, without re-executing successfully completed steps.
This is particularly useful for long-running workflows where you don't want to lose progress from successful steps when a single step fails.
When a workflow is resumed, it continues execution from the last failed step. A new workflow run ID is generated,
but the workflow maintains the state and results from previously completed steps.
You can make changes to the workflow code as long as these changes come after the failed steps.
However, making changes before the failed step will break the code and is not allowed.
For more details, check out [Handle workflow route code changes](/workflow/howto/changes) page.
## OpenAPI
````yaml /workflow/openapi.yaml post /v2/workflows/dlq/resume
openapi: 3.1.0
info:
title: Upstash Workflow REST API
description: >
Upstash Workflow is a serverless workflow orchestration service built on top
of Upstash QStash and Upstash Redis.
version: 2.0.0
contact:
name: Upstash
url: https://upstash.com
servers:
- url: https://qstash.upstash.io
security:
- bearerAuth: []
- bearerAuthQuery: []
paths:
/v2/workflows/dlq/resume:
post:
tags:
- DLQ
summary: Bulk Resume Workflows from DLQ
description: >
When a workflow run fails, it's automatically moved to the DLQ (Dead
Letter Queue) where it can be analyzed and resumed.
The resume feature allows you to continue a failed workflow run from exactly where it failed, without re-executing successfully completed steps.
This is particularly useful for long-running workflows where you don't want to lose progress from successful steps when a single step fails.
When a workflow is resumed, it continues execution from the last failed step. A new workflow run ID is generated,
but the workflow maintains the state and results from previously completed steps.
You can make changes to the workflow code as long as these changes come after the failed steps.
However, making changes before the failed step will break the code and is not allowed.
For more details, check out [Handle workflow route code changes](/workflow/howto/changes) page.
parameters:
- in: query
name: dlqIds
required: false
schema:
type: array
items:
type: string
description: >-
List of specific DLQ IDs to resume. If provided, other filters are
ignored.
- in: query
name: cursor
required: false
schema:
type: string
description: Pagination cursor for resuming workflows in batches.
- in: query
name: count
required: false
schema:
type: integer
description: >-
Maximum number of workflows to resume. If not provided, all matching
workflows will be resumed.
- in: query
name: fromDate
required: false
schema:
type: integer
format: int64
description: >-
Filter workflows by starting date, in milliseconds (Unix timestamp).
This is inclusive.
- in: query
name: toDate
required: false
schema:
type: integer
format: int64
description: >-
Filter workflows by ending date, in milliseconds (Unix timestamp).
This is inclusive.
- in: query
name: workflowUrl
required: false
schema:
type: string
description: Filter workflows by workflow URL.
- in: query
name: workflowRunId
required: false
schema:
type: string
description: Filter workflows by workflow run ID.
- in: query
name: workflowCreatedAt
required: false
schema:
type: integer
format: int64
description: >-
Filter workflows by creation timestamp in milliseconds (Unix
timestamp).
- in: query
name: label
required: false
schema:
type: string
description: Filter workflows by label assigned by the user.
- in: query
name: failureFunctionState
required: false
schema:
type: string
description: |
Filter workflows by failure function state.
| State | Description |
|--------|--------------|
| CALLBACK_INPROGRESS | The failure function is in progress. |
| CALLBACK_SUCCESS | The failure function run successfully. |
| CALLBACK_FAIL | The failure function failed to run. |
| CALLBACK_CANCELED | The failure function was manually canceled |
- in: query
name: callerIp
required: false
schema:
type: string
description: Filter workflows by IP address of the publisher.
- in: query
name: flowControlKey
required: false
schema:
type: string
description: Filter workflows by Flow Control Key.
- in: header
name: Upstash-Retries
required: false
schema:
type: integer
description: Override the number of retries for the remaining workflow steps.
- in: header
name: Upstash-Delay
required: false
schema:
type: string
description: >-
Override the delay before executing the next workflow step. Format
is `` (e.g., "10s", "5m").
- in: header
name: Upstash-Retry-Delay
required: false
schema:
type: string
description: >-
Override the retry delay expression for the remaining workflow
steps.
- in: header
name: Upstash-Flow-Control-Key
required: false
schema:
type: string
description: Override the flow control key for the remaining workflow steps.
- in: header
name: Upstash-Flow-Control-Value
required: false
schema:
type: string
description: >-
Override the flow control configuration in the format
`parallelism=, rate=, period=`.
- in: header
name: Upstash-Label
required: false
schema:
type: string
description: Override the label for the remaining workflow steps.
- in: header
name: Upstash-Failure-Callback
required: false
schema:
type: string
description: Override the failure callback URL for the remaining workflow steps.
responses:
'200':
description: Workflows resumed successfully
content:
application/json:
schema:
type: object
properties:
workflowRuns:
type: array
items:
type: object
properties:
workflowRunId:
type: string
description: >-
The ID of the resumed workflow run (a new ID is
generated for each resumed run).
workflowCreatedAt:
type: integer
format: int64
description: >-
The timestamp when the resumed workflow run was
created (Unix timestamp in milliseconds).
description: Array of resumed workflow runs.
cursor:
type: string
description: >-
Pagination cursor to use in subsequent requests. If empty,
all matching workflows have been processed.
'400':
description: Bad Request
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Some DLQ messages were not found
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'500':
description: Internal Server Error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
components:
schemas:
Error:
type: object
required:
- error
properties:
error:
type: string
description: Error message
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: QStash authentication token
bearerAuthQuery:
type: apiKey
in: query
name: qstash_token
description: QStash authentication token passed as a query parameter
````