workerfuse

Cloudflare spending limits vs pausing one Worker

Cloudflare now has spending limits for Workers and Durable Objects. They're account-wide and block the whole product. Here's how that compares to pausing only the runaway Worker.

Cloudflare shipped spending limits for Workers and Durable Objects. This is genuinely good news, I've wanted this for a while. You set a monthly dollar amount, and once it takes effect Cloudflare blocks that product's supported operations until the next billing period or until you raise the limit.

A few details worth knowing before you turn it on:

  • The limit is account-wide, per product. It can't target one Worker or one Durable Object namespace.
  • When it trips, it blocks new invocations for every Worker in the account (or every DO, for the DO limit). Cloudflare's own docs warn that a limit can interrupt every app that uses the product.
  • Workers and DOs have separate limits. KV, R2 and D1 aren't covered by them. AI Gateway has its own limits, but only for requests routed through a gateway.
  • It's monthly and counts after included usage. Blocking isn't instant, so it's not a guaranteed max invoice either.

Budget alerts still exist too, and they still just email you.

So which one?

Honestly, probably both. The native limit is a solid backstop for "something went very wrong this month". But if one Worker loops at 2am, an account-wide block takes your healthy Workers down with it.

That's the gap workerfuse fills. It checks every five minutes and pauses the Worker over its hourly or daily limit instead of the whole account. It also prices D1, KV, R2, Queues and Workers AI and charges them to the scripts bound to them (a shared resource counts against every script bound to it, so it can pause more than one). It's a safety net, not a billing cap: in our busy Durable Object test the spend-to-stopped gap was roughly 11 to 13 minutes, and that still costs money.

My gut says the setup that makes sense is a per-Worker pause with tight limits, and the native monthly limit set well above it as the last line of defense. One gotcha: if you self-host the guard, a native Workers block stops the guard's cron too, so it can't pause anything until you lift the block.

Pause the runaway Worker. Keep the rest running.

workerfuse checks your Cloudflare spend every five minutes and pauses any Worker over its limit.

Start free trial

Keep reading

How to build a per-Worker spending limit on Cloudflare

Read usage from GraphQL, price it, and deploy a stub version when one script goes over. The rough design, with the parts that bit me.

Cloudflare billing horror stories: four runaway bills from 2026

A $34,895 alarm loop, a $10,811 bill from an abandoned side project, a ~$36,000 queue loop, and $4,586 of D1 writes. What broke, how long it ran, and what Cloudflare did about it.

How a Durable Objects alarm loop runs up your Cloudflare bill

A Durable Object alarm that keeps rescheduling itself racks up requests, storage writes and duration. What that costs at list price, and how to stop it.