- Home
- Process Orchestration Software
- Cloudflare Workflows
Cloudflare Workflows
San Francisco, California, USA
What it is
Cloudflare Workflows lets developers build durable, multi-step applications on Cloudflare Workers without managing infrastructure. It can retry failed tasks, preserve state for minutes, hours, or weeks, and handle errors through durable steps. Workflows may pause for seconds, hours, or days, or wait for webhooks, user input, or external system responses. Instances can be triggered, paused, resumed, or terminated through code or an API. Integrations include Fetch API requests and Cloudflare services such as R2, KV, and D1. Workflows can be invoked through the Workers API, Wrangler CLI, or REST API. Billing covers CPU time, requests, persisted storage, and executed steps; sleeping or waiting does not incur CPU time. The Workers Free plan includes usage limits, while paid pricing starts at $5/mo. Paid plans allow up to five minutes of CPU time per invocation. A step can have unlimited wall-clock duration, subject to configured CPU limits. Workflows support human tasks and approvals, long-running workflows, versioning, and up to 50,000 concurrent runs. They cannot be deployed to Workers for Platforms namespaces.
For and against
For
- Free plan is available
- Automatic retries and persisted state
- Waits for webhooks or user input
- Integrates with R2, KV, and D1
- Supports 50,000 concurrent runs
Against
- Paid CPU time has invocation limits
- Usage billing covers several components
- Cannot deploy to Workers for Platforms
The verdict
Cloudflare Workflows provides durable orchestration with retries, waiting, state, and Cloudflare service integrations. Review usage limits and the deployment restriction before choosing it for a Workers architecture.
Who it suits
It is for developers building long-running, event-driven applications on Cloudflare Workers. It fits teams needing retries, persisted state, scheduled pauses, and API-controlled instances.
Plans and prices
Workers Free
100,000 requests per day shared with Workers · 10 ms CPU per invocation · 1 GB-month storage · 3,000 steps per day
Read 29 Sep 2026 · developers.cloudflare.com
Workers Paid
10 million requests per month included, then $0.30 per additional million · 30 million CPU milliseconds per month included, then $0.02 per additional million · 1 GB-month storage included, then $0.20/ GB-month · 500,000 steps per month included, then $0.80/ additional 100,000 per month
Read 29 Sep 2026 · developers.cloudflare.com
On the record
- API access
- Workflows can be invoked through the Workers API, Wrangler CLI, or REST API.developers.cloudflare.com · read 29 Sep 2026
- Deployment restriction
- Workflows cannot be deployed to Workers for Platforms namespaces because Workflows do not support Workers for Platforms.developers.cloudflare.com · read 29 Sep 2026
- Durable execution
- Workflows supports durable steps with automatic retries and error handling.developers.cloudflare.com · read 29 Sep 2026
- External events
- A Workflow can wait for webhooks, user input, or external system responses before continuing.developers.cloudflare.com · read 29 Sep 2026
- Instance management
- Workflow instances can be triggered, paused, resumed, and terminated programmatically or through an API.developers.cloudflare.com · read 29 Sep 2026
- Integrations
- The documentation identifies Fetch API requests and Cloudflare services including R2, KV, and D1 as services a Workflow can call.developers.cloudflare.com · read 29 Sep 2026
- 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.developers.cloudflare.com · read 29 Sep 2026
- Purpose
- Cloudflare Workflows lets developers build durable multi-step applications on Cloudflare Workers without managing infrastructure.developers.cloudflare.com · read 29 Sep 2026
- Retries and state
- Workflows can automatically retry failed tasks and persist state for minutes, hours, or weeks.developers.cloudflare.com · read 29 Sep 2026
- Scheduling
- Workflows can pause for seconds, hours, or days using step.sleep() and step.sleepUntil().developers.cloudflare.com · read 29 Sep 2026
- Support
- The Workflows documentation directs users to the Workers community on Discord to ask questions and discuss the platform.developers.cloudflare.com · read 29 Sep 2026
- Usage billing
- Workflows are billed for CPU time, requests, persisted storage, and executed steps, while waiting or sleeping does not incur CPU time.developers.cloudflare.com · read 29 Sep 2026
