Set a spending limit on Workers usage charges. The limit covers requests and CPU time across all Workers in your account, after included usage. It excludes the monthly subscription fee.
To configure a limit, follow Set a spending limit in the dashboard or Manage spending limits and alerts with the cf CLI.
Once the limit takes effect, Cloudflare rejects new invocations of your Workers, including:
- Incoming HTTP requests.
- Cron Triggers.
- Queue consumer invocations.
- Email Worker invocations.
- Calls from other Workers or Durable Objects.
HTTP visitors receive error 1103. This error has other causes, so check Billing > Spend Management before contacting support. Requests rejected by the spending limit are not billed as Worker invocations.
Static assets served without running your Worker continue to be available. Requests that need Worker code, such as requests routed through run_worker_first, can fail. A limit does not delete your Workers or assets.
A Workers limit applies to the whole account, rather than one application or environment. For example, a test Worker can reach the shared limit and interrupt a production Worker in the same account.
Durable Objects, Workers KV, R2, and other products have separate charges. A Workers spending limit does not apply to those charges. A Durable Object can also fail when it calls a Worker whose limit has been reached.
A spending limit is not an exact maximum bill. Usage reporting and blocking take time, so usage can continue after the threshold is reached. The Workers Paid subscription fee remains payable.
For a limit on the CPU time of each invocation, configure CPU time limits. For an email without blocking invocations, use an email alert.
Raise the limit above current spend, turn it off, or remove it. Changes can take a few minutes to apply.
The block also expires at the start of the next subscription billing period. An enabled limit remains in place for that new period.