# Durable Objects, Workers - Durable Objects now defer code updates by default

Publisher-attributed story with a reviewed brief or permitted publisher paragraph. The original publisher is responsible for the linked reporting.

- Publisher: Cloudflare Developers
- Category: Cloud
- Original publication time: 2026-10-30T00:00:00Z
- First observed by NexusTechWire: 2026-10-30T18:50:38Z
- Original source: https://developers.cloudflare.com/changelog/post/2026-10-30-durable-objects-deferred-code-updates/
- NexusTechWire record: https://nexustechwire.com/news/news-2e90cf7c382beb356eae

## From the publisher

Durable Objects can stay active across requests, allowing you to run long-running agents, maintain long-lived WebSocket connections and coordinate state across many clients. This is possible because each Durable Object is globally unique, and this means it must run only one version of your code at a time. Previously, when you deployed a change to your Durable Objects code, that change would be applied immediately, which could interrupt in-flight work and terminate open connections. Durable Objects now defer code updates by default. When you deploy, an active Durable Object can keep running its current code for up to 5 minutes (300 seconds) while it waits to hibernate. This gives in-flight work time to finish. WebSocket connections that use the Hibernation API remain connected when an object adopts new code after hibernating.

Source license: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Publisher excerpt shortened and converted to plain text. Original source license applies.

Read the full original: [Cloudflare Developers](https://developers.cloudflare.com/changelog/post/2026-10-30-durable-objects-deferred-code-updates/)

This record does not reproduce the complete article or represent independent confirmation of every source claim.
