Pricing

• A step is the execution of a single workflow step in your workflow.
• From a billing perspective, each executed step is counted as one billed step.
• If a step execution fails and is retried, each retry is counted as an additional billed step.
• Different step types consume a different number of billed steps:
  • context.run, context.sleep, context.sleepUntil, and context.waitForEvent generate ONE billed step.
  • context.call and context.invoke generate TWO billed steps.
  • When steps are executed in parallel, each step generates ONE extra billed step.

• These are soft limits and apply only if you consistently exceed your quota.
• Short or occasional spikes will not immediately block step executions.
• If usage continues to exceed the limit, we will contact you to discuss an upgrade:
  • Fixed 1M → Fixed 10M
  • Fixed 10M → Custom Enterprise plan
• If we are unable to reach you and limits are still exceeded over time, workflow runs may start failing with quota errors.

Workflow is built on top of QStash. When the daily steps limit is reached:

• QStash starts returning errors for step execution.
• The Workflow SDK throttles execution and retries after a short delay.
• If the retry limit is reached, the workflow run fails.
• Failed runs are recorded in the DLQ (Dead Letter Queue).

• There is no requests-per-second (RPS) limit for Workflow execution APIs.
• APIs used for logs, messages, and other management features do have RPS limits. When exceeded, the API returns a 429 Too Many Requests error.

• Since Workflow execution does not have an RPS limit, QStash enforces a Max Concurrent Steps limit:

  • Workflow accepts all step executions.
  • If usage is too high, execution is slowed down by limiting how many steps run in parallel.
  • Additional steps are queued and executed later.

  See “Max Concurrent Steps” in the pricing table for details.

• When a workflow run is triggered, if the request body exceeds the size limit, the API returns an HTTP 412 error.
• The Workflow SDK logs the error, marks the workflow run as failed, and records it in the DLQ (Dead Letter Queue).
• Between steps, the Workflow SDK makes calls to QStash. Responses from context.run, context.call, and context.invoke are also subject to the max message size limit.
• If these responses exceed the limit, the workflow run fails and is recorded in the DLQ.