Count Cloudflare Workflows steps before August billing starts
Cloudflare Workflows now has per-step pricing in its billing model, with step and storage billing scheduled to start no earlier than August 10, 2026. Teams using durable agent or automation flows should measure step counts before costs begin.
Cloudflare has confirmed that Workflows pricing now includes per-step billing. Confidence level: confirmed. The new step and storage charges are scheduled to start no earlier than August 10, 2026, so teams running durable automation, agent jobs, or long-lived business processes should measure step volume now instead of waiting for the first invoice.

What changed
Cloudflare updated Workflows pricing on July 7, 2026. Requests and CPU time billing have already been enabled since the public beta, but the model now explicitly adds steps as a billed dimension. Cloudflare defines a step as each unit of work executed by a Workflow, including operations such as sleeping or waiting for events.
The pricing docs now list four Workflows billing dimensions: CPU time, requests, storage, and steps. Storage and step billing apply to Workers Paid plans starting no earlier than August 10, 2026. Workflows remain available on both Workers Free and Workers Paid plans, but teams should not treat every paused or retry-heavy workflow as cost-neutral.
| Cost surface | What Cloudflare counts | Current action | Caveat |
|---|---|---|---|
| Requests | Workflow invocations | Track launch and retry volume | Shared with Workers request limits |
| CPU time | Active compute used by a Workflow | Keep heavy work bounded | Idle waiting does not incur CPU time |
| Storage | Persisted Workflow state in GB-months | Review long-running state retention | Billing starts no earlier than August 10 |
| Steps | Each executed unit of work | Query stepCount and audit loops | Sleep and wait operations can still count as steps |
Why this is early
This is official Cloudflare platform news, not a rumor. The primary source is Cloudflare's own July 7 changelog entry, and the Workflows pricing and metrics docs already reflect the new step dimension.
It is early operationally because billing has not started yet for steps and storage. That gives teams a short measurement window before August 10. LinkLoot will treat changes to the start date, included allowances, or per-step rates as update triggers.
Key takeaways
- Cloudflare Workflows now has four billing dimensions: CPU time, requests, storage, and steps.
- Step and storage billing starts no earlier than August 10, 2026.
- A step includes Workflows operations such as sleeping or waiting for events, not only active business logic.
- Cloudflare says
stepCountis available through Workflows analytics via the GraphQL Analytics API. - Agent pipelines should audit retries, polling loops, wait states, and fan-out patterns before the billing date.
Availability and access
The pricing change applies to Cloudflare Workflows on Workers Paid plans. Workflows is still included in both Free and Paid Workers plans, but the August billing note is tied to step and storage usage on Paid plans.
Cloudflare has not made the final invoice impact obvious from a single example because it depends on workflow shape. A short checkout flow and a long-running agent job can have very different step counts even if both look like one automation from the product surface.
Practical LinkLoot angle
This is a cost-model change for automation builders. If you use Workflows for AI agents, webhook orchestration, ecommerce order handling, background processing, or customer onboarding, the important question is no longer just "does it finish?" It is "how many billable units does it burn while finishing?"
Use the next few weeks for a small cost review:
Cloudflare Workflows billing check
- Query recent Workflow analytics and group by workflow name and step count.
- Flag workflows with sleeps, waits, retries, polling, or large fan-out loops.
- Test whether failed retries multiply step usage in real scenarios.
- Compare Workflows with Queues, Durable Objects, Workers, or cron-style jobs for simple tasks.
- Add alerts for sudden changes in instance count, duration, and step volume.
For AI-heavy automations, pair that review with LinkLoot's AI workflow automation guide so model calls, retries, and orchestration costs are checked together.
What to verify before you act
- Confirm the latest Workflows pricing table before August 10, 2026.
- Check whether your account is on Workers Free or Workers Paid.
- Query
stepCountin Cloudflare Workflows analytics for your highest-volume workflows. - Review whether sleeps, waits, retries, and event waits are necessary or can be batched.
- Re-run the estimate after any product launch, traffic spike, or agent workflow change.
Source check
Confirmed by:
- Cloudflare's July 7, 2026 changelog says Workflows pricing now includes per-step billing and that step and storage billing starts no earlier than August 10, 2026.
- Cloudflare's Workflows pricing documentation lists CPU time, requests, storage, and steps as billing dimensions.
- Cloudflare's metrics documentation confirms Workflows analytics expose fields including
stepCountthrough the GraphQL Analytics API.
Early signal / context:
- The billing start date is future-facing. Treat August 10 as the earliest start, not a guarantee that every account's final bill impact is known today.
Cloudflare says step and storage billing will start no earlier than August 10, 2026.
