wrangler Workflows configures per-instance step limits

Introduced 2026-03-03 · score 0.94

HOW TO USE IT

When a Workflow needs a per-instance step cap, set `workflows[].limits.steps` to an integer from 1 to 25,000; the default is 10,000. Run `wrangler dev` to enforce the configured limit locally.

{
  "workflows": [{
    "name": "<workflow-name>",
    "binding": "<binding-name>",
    "class_name": "<class-name>",
    "limits": { "steps": 5000 }
  }]
}

WHY THIS HELPS

Set a maximum step count for a Workflow instance and reproduce that limit in local development.

BEFORE THIS CHANGE

Instances were limited to 1,024 steps.

REQUIREMENTS AND LIMITATIONS

Version: 4.70.0
workflows[].limits.steps: Maximum steps per Workflow instance; integer from 1 to 25,000. Defaults to 10,000 when omitted.
workflows[].name (required): Workflow name.
workflows[].binding (required): Binding name used to access the Workflow.
workflows[].class_name (required): Workflow class name.
Prerequisite: The configurable 10,000–25,000 step limit applies to Workflows on Workers Paid; Workers Free has a 1,024-step limit.
The `steps` value must be an integer between 1 and 25,000.
The default limit is 10,000 steps when not specified.
Docs conflict: The current general Wrangler configuration page says limits are enforced only when deployed, while the Wrangler 4.70.0 release note specifically says Workflow step limits are enforced by `wrangler dev` locally. https://developers.cloudflare.com/workers/wrangler/configuration/

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card

Tools change faster than your agent’s training data.

Changes

wrangler Workflows configures per-instance step limits