// AI Platform Drift
Cloudflare Workers exception handling changes 15 September 2026
Cloudflare developer changelog · published 2026-10-23 17:10 UTC
WHAT CHANGEDCloudflare Workers compatibility flag spec_compliant_dispatch_exceptions becomes default on 2026-09-15. When an event listener throws during dispatchEvent(), remaining listeners will continue to run instead of being skipped. Exceptions are reported via global error event and console. Affects dispatchEvent(), AbortSignal abort dispatch, and runtime-fired events on WebSocket, EventSource, and MessagePort. Legacy Service Worker addEventListener("fetch") is not affected.
WHY IT MATTERSCode that depends on exceptions halting event dispatch will break. If your error handlers assume no subsequent listeners run after a throw, those assumptions become invalid. Multi-listener event chains that previously stopped on first error will now execute fully, potentially running cleanup or state-change logic you expected to skip.
WHAT TO DOAudit event listeners in Workers code for exception-throwing paths, especially on WebSocket, EventSource, MessagePort, and AbortSignal. If you rely on exceptions stopping dispatch, add no_spec_compliant_dispatch_exceptions to compatibility_flags before 2026-09-15. If your compatibility_date is before 2026-09-15, you have until you update that date.
ACT-BY DATE PASSED — this item's act-by date, 2026-09-15, is before this page was generated 2026-11-21 (UTC). Check the primary source before acting on it.
Model-reported confidence 95% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Workers - Spec-compliant dispatchEvent() exception handling +https://developers.cloudflare.com/changelog/post/2026-08-19-spec-compliant-dispatch-exceptions/ +Wed, 19 Aug 2026 00:00:00 GMT + +A new compatibility flag, spec_compliant_dispatch_exceptions, aligns the Workers runtime's event dispatch behavior with the DOM specification ↗︎. This flag becomes the default for all Workers with a compatibility date of 2026-09-15 or later. +Previously, when an event listener threw an exception during dispatchEvent(), the runtime propagated the exception immediately and skipped all remaining listeners for that event. The spec instead requires that listener exceptions are reported (via the global error event and the console) without interrupting the dispatch — remaining listeners still run. +This change affects the JS-visible dispatchEvent(), AbortSignal abort dispatch, and runtime-fired events on WebSocket, EventSource, and MessagePort. Top-level event delivery for legacy Service Worker syntax entry points (such as addEventListener("fetch", ...)) is not affected. +To opt in before the default date, add spec_compliant_dispatch_exceptions to your compatibility_flags. To preserve the old behavior after the default date, use no_spec_compliant_dispatch_exceptions. +For more details, refer to the compatibility flags documentation.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.5 |
|---|---|
| triage reasoning | Breaking change to event dispatch exception handling with mandatory adoption date affects all Workers deployed after 2026-09-15. |
| signals | future default date: 2026-09-15 · breaking behavior change: exception handling in dispatchEvent() · compatibility flag required for opt-out after default date · affects multiple runtime components: WebSocket, EventSource, MessagePort, AbortSignal · spec compliance change alters listener execution flow |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |