Source-linked reports: Amounts and outcomes come from the original reports and linked replies.
Ajay Sohmshetty: a Workflows cost-estimate email projects $35/month rising to $38,277/month; Cloudflare says the estimate was a mistake.
Ajay Sohmshetty (@AjaySohmshetty) posted a screenshot of a Cloudflare email and wrote that the bill was going from $35/month to $38,277/month. In the thread he explains that Workflows had charged only for underlying Worker CPU time and that the pricing was moving to a steps-based model. The figures are a projected estimate from that email, not an amount billed or charged. Replying publicly, mia (@miacmal) said it was a mistake on Cloudflare's end and that a corrected estimate would be sent; Cloudflare Workflows engineering manager James Delorey told another affected user an updated estimate would be sent soon.
What happened
- Reported cause
- Unknown
- Incident date
- Date not recorded
- First reported
- 2026-07-16 13:50 UTC
- Billing outcome
- Not recorded
- Case progress
- Not established
- Public Cloudflare reply
- Personnel reply linked
Latest reported outcome
The $35/month and $38,277/month figures come from a cost-estimate email, not a bill, so no reported charge is recorded. Cloudflare staff said the estimate was wrong and a corrected one would be sent; the author said the pricing model still shifts to steps-based billing. No corrected figure is recorded yet.
View this update in the timelineOriginal sources
- Author post with the estimate email
- mia (@miacmal) reply: mistake, corrected estimate coming
- Cloudflare Workflows engineering manager reply
Each entry links to the report or reply it describes.
Case timeline
Author posts the estimate email
Read on 𝕏The author says the bill is going from $35/month to $38,277/month, citing a Cloudflare email.
Ajay Sohmshetty
@AjaySohmshetty · Original 𝕏 post
Woke up to see our @Cloudflare bill going from $35/month ➡️ $38,277/month "uhhh... This feels existential" - @andrewk17 https://t.co/dZSZNY1x7l
Author explains the pricing change
Read on 𝕏The author says Workflows had charged only for Worker CPU time and is moving to steps-based pricing without warning.
Ajay Sohmshetty
@AjaySohmshetty · Original 𝕏 post
For context- Cloudflare’s durable execution platform, Workflows, originally only charged for underlying Worker usage, which is CPU-time based rather than clock-time based. In fact, we picked Cloudflare for this exact reason: most of our workflows involve waiting (ex. polling, waiting for network requests to come back), so it was far cheaper for us to use Cloudflare than @temporalio or @inngest for instance. These other durable execution platforms also charge based on “steps” - which I always thought was dumb, because it disincentivizes the best practice of decomposing workflows into small units of work in the form of steps. But unfortunately it seems Cloudflare is following suit, without warning… Feeling blindsided after we’ve already fully built all of our durable workflows on Cloudflare
Staff says the estimate was a mistake
Read on 𝕏mia (@miacmal) replies: "this was a mistake on our end… we are working to get a corrected estimate sent out as soon as possible".
mia
@miacmal · Original 𝕏 post
@AjaySohmshetty @Cloudflare @andrewk17 hello, this was a mistake on our end. apologies for the confusion. we are working to get a corrected estimate sent out as soon as possible
Author updates the thread
Read on 𝕏The author says Cloudflare appears to have sent incorrect cost estimates, while the model still shifts to steps-based pricing.
Ajay Sohmshetty
@AjaySohmshetty · Original 𝕏 post
Update: it appears that Cloudflare sent incorrect cost estimates. We’ll see what the updated numbers look like, but it doesn’t change the fact that the pricing model has fundamentally shifted to a “steps” based one. Have otherwise had a wonderful experience with Cloudflare so hoping the situation can be rectified for everyone 🙏🏽
Engineering manager promises an updated estimate
Read on 𝕏James Delorey tells another user in the thread that an updated estimate will be sent out soon.
James Delorey
@deloreyjmi · Original 𝕏 post
@appfactory @miacmal @AjaySohmshetty @Cloudflare @andrewk17 hey Peter, an updated estimate will be sent out soon. sorry for the scare. feel free to get in touch with Mia or me in the meantime if you have additional questions
More to read
A budget alert is a horn, not a brake
@GUYUE_LGY points to Cloudflare’s Budget alerts documentation: alerts send email when spend crosses a threshold but do not pause or cap usage. Before letting AI run unattended, the author checks what actually happens at the line.
mcwangcn reports $1,300 in D1 charges after a bot attack.
@mcwangcn says D1 writes previously cost over a thousand dollars and separately mentions Workers CPU charges without giving an amount. He later shares a Cloudflare bill and says $1,300 of its $3,600 came from D1 after a bot attack.
How I keep Cloudflare under $5: where surprise bills come from
Ashish Sharma (@sarmaasis) runs several sites on the $5 Workers Paid plan and lists, product by product, the usage patterns he says quietly run up a Cloudflare bill, ending with a 12-item checklist.