Cloudflare Workflows
Use Workflows for durable, multi-step jobs that must retry, wait, and resume without losing completed work. An instance is one execution; steps define persistence and retry boundaries.
Fetch the relevant current documentation before implementing. API shapes, configuration, testing helpers, limits, and examples belong in the docs rather than in this reference.
- Start a project: Build your first Workflow covers scaffolding, configuration, deployment, and a first instance.
- Design durable execution: Rules of Workflows covers step boundaries, replay, state, and idempotency.
- Implement or manage an instance: Workers API covers steps, instance operations, parameters, and return types.
- Check capacity and cost: fetch limits and pricing for the target plan.
In This Reference
- configuration.md — setup, bindings, retry configuration, and local development
- api.md — steps, instance lifecycle, events, CLI, and REST operations
- patterns.md — design decisions, examples, orchestration, and tests
- gotchas.md — failures, timeouts, replay, and capacity investigation
See Also
- Durable Objects — stateful coordination
- Queues — asynchronous message delivery
- Workers — application entry points that trigger instances