If you run a long-lived agent on Cloudflare Workflows, your bill is about to grow a new dimension — two, actually — and the way you were taught to write durable code is what makes it grow.
In a changelog dated July 7, Cloudflare said Workflows will start billing for step operations and stored state no earlier than August 10, 2026. Workers Free plans won't be charged beyond their included amounts. Workers Paid workloads will. It reads like a routine pricing note. For anyone using Workflows as an agent runtime, it's a nudge to go re-read your own code.
Four dimensions now, and the new two are the agent-shaped ones#
Workflows now meters on four things: CPU time, requests (invocations), storage (persisted state, in GB-months), and steps (each unit of work a workflow executes). CPU and requests you were already paying. Storage and steps are the additions — and they map almost exactly onto how a durable agent is built.
The detail to sit with is what counts as a step. Per Cloudflare's pricing, a step is each unit of work — and step operations include sleeping and waiting for events. Not just active compute. The wait itself.
A sleep is a step. The day your agent spends parked, waiting for a human to click approve, is now a line item — twice: once as a step operation, and again as the state you kept alive to resume it.
Why this hits durable agents specifically#
Durable execution sells you two habits, and both are now billed.
The first is wrap each retryable unit in its own step. That's not gold-plating — it's how you get exactly-once semantics and the ability to resume mid-run after a crash. The natural consequence is a lot of steps, because granularity is what buys you correctness.
The second is sleep, don't poll-and-die. A long-running agent waiting on a human approval or an external webhook is supposed to sleep or waitForEvent for as long as it takes — hours, days — and wake up intact. That durable wait is the whole point of the pattern. It's also, now, a billed step, plus GB-months for every paused run you keep parked.
So the same properties that made Workflows attractive for agents — fine-grained steps, multi-day waits, persisted state you can resume — are the properties the new meter reads. This isn't a gotcha aimed at you; it's the cost of the durable-execution model finally showing up on the invoice. But it lands hardest on exactly the workloads that adopted it most enthusiastically.
What to do before August 10#
Not panic, and not flee. Reshape.
- Measure your exposure first. Pull per-workflow step counts and persisted-state size from the dashboard and analytics. You cannot reason about a bill you haven't counted, and the two new dimensions were free until now, so almost no one has looked.
- Collapse steps that don't need to be durable. A step earns its keep only if it needs independent retry or a resume boundary. Wrapping a pure, deterministic function in a step to "be safe" now buys you a line item and no durability you didn't already have. Coarser steps, fewer of them.
- Externalize or shorten the long waits. A workflow that sleeps three days on a human is the most exposed shape there is. Where you can, move the human-in-the-loop wait to a cheaper primitive and re-enter the workflow on the answer — the durable-interrupt pattern is the same idea, just priced. Where you can't, at least know what each parked run costs.
- Garbage-collect state. Storage is GB-months. Finished runs you never clean up, oversized checkpoints, state you persist "just in case" — that all accrues now. Trim what you keep alive.
The real lesson under the pricing note#
"Just make everything a step" was always slightly lazy engineering that the free tier let you get away with. Fine-grained-by-default is easy to write and hard to reason about; coarse, deliberate steps are what durable-execution veterans recommend anyway. Cloudflare's meter is about to make the disciplined version the cheap version too.
That's the useful way to read August 10. Not "Workflows got more expensive," but "the durable-execution tax moved from invisible to itemized, and the fix for the bill is also the fix for the design." Price the shape of your agent. Then keep building on the tool — just with fewer, better steps.
