PuppyIP Resource Center
Cloud Operations 7 minutes Published 2026-11-14

Cloudflare spending limits: Workers 1103, continuing costs and recovery

Workers and Durable Objects spending limits are account-wide, product-specific pause controls for the current subscription period. Email alerts only notify you; they do not pause service. Neither control guarantees a capped invoice. Choose alert-only to keep service running, or assess every affected application before enabling a pause.

Cloudflare Workers Durable Objects Spending limits Billing alerts Cloud operations

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • On November 13, 2026, Cloudflare announced account-wide spending limits and alert-only policies for Workers and Durable Objects. You need permission to edit billing settings. The source material does not list exact plan or country availability, so check whether the controls appear in your account.
  • Workers and Durable Objects have separate limits covering combined product usage across your account. You cannot scope one to an individual Worker, namespace or billing metric, so test and production workloads share the relevant limit.
  • Limits use estimated usage after included amounts are deducted. Reporting, in-progress work and enforcement can lag. Durable Objects stored data and the Workers Paid subscription fee may still incur charges, so a spending limit is not a guaranteed invoice cap.
  • Some work can be blocked after a threshold while existing WebSocket messages, in-flight duration, certain legacy KV operations and pending alarms follow separate rules. After lifting a pause, check Workers, objects and alarm recovery individually.

What do these controls cover? Separate alerts from pauses

On November 13, 2026, Cloudflare announced new spending controls for Workers and Durable Objects. You can set a spending limit for either product or choose email alerts without a pause. Each policy covers the whole account for the current subscription billing period; it cannot target one Worker, Durable Object namespace or billing metric. Test and production workloads in the same account draw on the same product limit, and dependencies can be affected too.

The dashboard path is Billing > Spend Management, and the person making changes needs permission to edit billing settings. The official material does not list exact plan or country availability, so check your own account for the control. Workers and Durable Objects have separate policies. Account-wide Budget Alerts only notify you about overall usage, while AI Gateway spending controls apply to requests routed through the gateway and can be scoped by user, model or provider; these controls are not interchangeable.

Which charges count, and which can continue?

Limits use estimated US-dollar usage charges for the current subscription period, after included usage is deducted. Workers counts requests and CPU time. Durable Objects counts requests, duration, SQLite rows read and written, and key-value storage reads, writes and deletes. The Workers Paid subscription fee and other product charges are outside the Workers limit; Durable Objects stored-data charges and the shared Workers Paid subscription fee are also excluded from the object limit.

Stored Durable Objects data can continue to incur charges while the objects are paused. Metering and enforcement are not immediate: an operation already in progress may keep running, and enforcement may be delayed or fail. Recorded spending can therefore exceed the threshold. A spending limit is not a hard bill cap; the invoice is the final record of charges.

Will an alert pause service? How do email notifications work?

No. An alert-only policy emails you when spending reaches its threshold and leaves the product running. To pause supported operations, configure a spending limit. Policies with a notification email send messages at 80% and 100% of the threshold. If usage passes both points between evaluations, you may receive only the 100% email.

A limit created in the dashboard does not automatically include a notification recipient; configure an email address separately. On means the policy is enabled, not that the service is currently healthy. Limit reached records a threshold event, but does not confirm that blocking has finished propagating. Audit history shows policy changes and threshold events; it cannot by itself prove that an email arrived or a pause took effect.

Check the shared scope and recorded usage before saving

In Billing > Spend Management, choose Workers or Durable Objects and select Edit the spending limit. The amount must be greater than zero and can have up to two decimal places. Saving a new limit turns it on; editing an existing limit preserves its current On or Off state. Usage already recorded in the current period counts. For example, if Workers has reached $60 before you save a $50 limit, Cloudflare may pause new invocations soon after it evaluates the policy.

Inventory the production, test and dependent services using that product in the account, and decide who will receive alerts. A Workers limit can prevent a calling Durable Object from continuing; a Durable Objects limit can also cause an application that depends on those objects to fail. Choose alert-only if service must keep running. If you choose a pause, plan for its shared impact and for charges that remain outside the limit.

What does error 1103 mean when the Workers limit takes effect?

Once the limit takes effect, Cloudflare rejects new Worker invocations, including HTTP requests, Cron Triggers, Queue consumers, Email Workers, and calls from other Workers or Durable Objects. HTTP visitors may see error 1103, but that error has other causes too; check Billing > Spend Management as part of diagnosis. Invocations rejected by the spending limit are not billed as Worker invocations.

Static assets served without running Worker code can remain available. A request routed through run_worker_first needs Worker code and may fail. The pause does not delete Workers or assets. After lifting the policy, confirm that the application call path has recovered.

What does a Durable Objects pause block, and what remains?

Once the limit takes effect, new Durable Object stub requests, SQL reads and writes, SQLite storage growth, and new alarms created with setAlarm() are rejected. Pending alarms are held without using their normal retry budget, but an alarm scheduled more than seven days ago is deleted while held. After the block ends, alarms still within that seven-day window can run. If deleted work is still needed, your application must schedule it again.

A pause does not stop messages on already-open WebSocket connections or duration charges for requests already running. It also does not block key-value operations in legacy KV-backed objects, even though those operations count toward the limit. Existing stored data can keep accruing storage charges. When service resumes, check delayed work and object state instead of assuming every operation retried automatically.

How do you lift a pause and handle the next period?

During the current period, raise the limit above current spending, turn it Off, or remove it. Changes can take a few minutes to apply, and new usage can incur charges once service resumes. Turning the same limit off and on does not reset spending already recorded for the period. Before restoring service, review current usage, the limit needed to resume, and the notification recipient; then check Workers and Durable Objects separately.

A pause expires automatically when the next subscription billing period starts, but an enabled limit stays configured for the new period. If your subscription renews on the 15th, that renewal date—not the first day of the calendar month—marks the reset. These actions lift only a block caused by a spending limit; they do not remove other account or product restrictions. After restoring Durable Objects, reschedule any deleted alarms whose work is still needed.

Sources

Frequently Asked Questions

Should I use the account spending limit to restrict CPU time for one Worker invocation?

They control different things. A spending limit covers the account’s combined Workers request and CPU charges for the subscription period. Use CPU time limits to restrict CPU time per invocation. A per-invocation limit is not an account bill cap; follow the official Workers documentation linked here for that configuration.

Does pausing Durable Objects delete the objects or their existing data?

No. A spending limit does not delete objects or their stored data, and stored-data charges can continue. Pending alarms have a separate seven-day retention boundary, so retained data does not mean every scheduled job is retained.

Do these limits already cover other Cloudflare products?

The November 13, 2026 announcement and the documentation checked for this article support Workers and Durable Objects; support for more products is still planned. A Workers limit does not control Workers AI, KV, R2 or other product charges. AI Gateway request budgets are a separate control.