Cloudflare Workflows
developers.cloudflare.com
What it is
Cloudflare Workflows lets developers build durable, multi-step applications on Cloudflare Workers without managing infrastructure. It automatically retries failed tasks, handles errors, and preserves state for minutes, hours, or weeks. Workflows can pause for seconds, hours, or days, or wait for webhooks, user input, or external system responses before continuing. Instances may be triggered, paused, resumed, or terminated through code or an API. A workflow can call Fetch API requests and Cloudflare services including R2, KV, and D1, and can be invoked through the Workers API, Wrangler CLI, or REST API. Billing covers CPU time, requests, persisted storage, and executed steps; waiting or sleeping does not incur CPU time. Workers Free includes a free plan with usage limits, while paid pricing starts at $5/mo. Paid plans allow up to five minutes of CPU time per invocation. The service has a cloud deployment model, supports human tasks and approvals, long-running workflows, versioning, and up to 50,000 concurrent runs. Workflows cannot be deployed to Workers for Platforms namespaces.
Spec sheet
- Purpose
- Cloudflare Workflows lets developers build durable multi-step applications on Cloudflare Workers without managing infrastructure.Read 29 Sep 2026 · developers.cloudflare.com
- Integrations
- The documentation identifies Fetch API requests and Cloudflare services including R2, KV, and D1 as services a Workflow can call.Read 29 Sep 2026 · developers.cloudflare.com
- Support
- The Workflows documentation directs users to the Workers community on Discord to ask questions and discuss the platform.Read 29 Sep 2026 · developers.cloudflare.com
- Headquarters
- San Francisco, California, USARead 28 Sep 2026 · developers.cloudflare.com
- Founded
- 2009Read 28 Sep 2026 · developers.cloudflare.com
- API access
- Workflows can be invoked through the Workers API, Wrangler CLI, or REST API.Read 29 Sep 2026 · developers.cloudflare.com
- Deployment restriction
- Workflows cannot be deployed to Workers for Platforms namespaces because Workflows do not support Workers for Platforms.Read 29 Sep 2026 · developers.cloudflare.com
- Durable execution
- Workflows supports durable steps with automatic retries and error handling.Read 29 Sep 2026 · developers.cloudflare.com
- External events
- A Workflow can wait for webhooks, user input, or external system responses before continuing.Read 29 Sep 2026 · developers.cloudflare.com
- Instance management
- Workflow instances can be triggered, paused, resumed, and terminated programmatically or through an API.Read 29 Sep 2026 · developers.cloudflare.com
- Limits
- A Workflow step has unlimited wall-clock duration, but its CPU time is subject to the configured limit; paid plans allow up to five minutes of CPU time per invocation.Read 29 Sep 2026 · developers.cloudflare.com
- Retries and state
- Workflows can automatically retry failed tasks and persist state for minutes, hours, or weeks.Read 29 Sep 2026 · developers.cloudflare.com
- Scheduling
- Workflows can pause for seconds, hours, or days using step.sleep() and step.sleepUntil().Read 29 Sep 2026 · developers.cloudflare.com
- Usage billing
- Workflows are billed for CPU time, requests, persisted storage, and executed steps, while waiting or sleeping does not incur CPU time.Read 29 Sep 2026 · developers.cloudflare.com
Plans and prices
Strong points and limits
Strong points
- Retries failed tasks automatically
- Persists workflow state for weeks
- Waits for webhooks or user input
- Calls R2, KV, and D1
- Free plan included with Workers Free
Limits
- Usage limits apply on the free plan
- Paid usage is billed by resource consumption
- Paid invocations allow five minutes of CPU time
- Cannot deploy to Workers for Platforms namespaces
Who it suits
It suits developers building long-running, event-driven applications on Cloudflare Workers. Teams needing retries, persisted state, scheduling, external-event waits, or API-triggered instance control can use it.
Verdict
Cloudflare Workflows provides durable execution, scheduling, state, and event waits for Workers applications. Review usage limits, resource-based billing, CPU limits, and deployment restrictions before choosing a plan.
Where Specifiction places it
- Process Orchestration Software#14 of 317.8