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

Cloudflare Workers request.signal: November 17 default and fetch cancellation

The November 17 default depends on each Worker’s compatibility date. request.signal reports client disconnects; pass it explicitly to let downstream fetches respond.

Cloudflare Workers request.signal AbortSignal Compatibility dates

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

  • From November 17, 2026, Workers with a compatibility date of 2026-11-17 or later receive client-disconnect events through request.signal by default.
  • As of November 14, the scheduled default change is still in the future; existing Workers keep their current behavior until their compatibility date or flags change.
  • An abort event is a disconnect notification; pass { signal: request.signal } to an outgoing fetch if you want it to respond to that signal.
  • request_signal_passthrough is a separate compatibility flag, and this default change does not enable it.
  • Check dates, flags, and downstream API support per Worker; the signal does not undo completed work or set a billing cap.

When the default changes

Cloudflare’s November 2, 2026 changelog says that Workers with a compatibility date of 2026-11-17 or later will receive client-disconnection events through the incoming request’s request.signal by default. For those dates, you will no longer need enable_request_signal just to receive the event. The signal gives your code a way to respond when a client leaves.

The condition applies to each Worker’s compatibility date. As of November 14, the scheduled date is still in the future. Neither the calendar nor the date of a code release proves that a particular deployment uses the new behavior.

Check the date and flags on existing Workers

Existing Workers keep their current behavior until their compatibility date or relevant flags change. Check the settings actually applied to the Worker you are investigating; Workers in the same project may use different dates and flags.

To try the behavior early with a compatibility date before 2026-11-17, add enable_request_signal. With a date of 2026-11-17 or later, add disable_request_signal to opt out. Before changing anything, confirm which flags apply to that Worker so you do not assume one deployment’s behavior applies to another.

An abort event is a cancellation notification

When the client disconnects, the incoming request’s AbortSignal fires an abort event. A Worker can listen for it to record the disconnect or clean up resources it created and still controls; the listener gives your application a chance to respond, while your code defines the right cleanup boundary.

Receiving the event does not force every line of code, Promise, or remote service to stop. Work must observe and handle cancellation to respond to it. Queued work and remote writes still have their own lifecycles.

Pass the signal to outgoing fetch calls

Receiving an incoming signal by default does not attach it to every outgoing request. To make an AbortSignal-aware fetch respond to the client disconnect, pass the signal explicitly—for example, fetch(url, { signal: request.signal })—and confirm it reaches the layer that actually makes the network request.

request_signal_passthrough is a separate compatibility flag, and this default change does not enable it. The announcement demonstrates passing the signal explicitly. Observing a disconnect does not prove that downstream work was cancelled.

Check behavior on a low-impact path

Choose a low-impact test route that does not write business data. Disconnect a test client and observe whether abort fires. Separately check whether the outgoing fetch receives that signal and reports cancellation. A Worker log confirms that the event was observed; it cannot establish that a remote service stopped.

This capability provides a cancellation signal; it is not a billing cap and cannot roll back business operations that have already completed. The announcement does not promise automatic cost savings or a performance increase. For requests that write data, apply your own rules to decide what has completed and what still needs processing or recovery.

Sources

Frequently Asked Questions

What time and time zone does the November 17 change use?

The reviewed announcement and compatibility documentation specify 2026-11-17 but give no exact switching time or time zone. Assess an individual Worker through its compatibility date, flags, and observed behavior; do not invent an account-wide switching schedule.

Does the announcement list extra charges, plan limits, or regional exclusions?

These documents do not list extra charges or exclusions for particular plans or regions for this change. That is not verification of availability for every account. Check your own configuration and current official information where account conditions matter.