Lifecycle of a Durable Object

There was a discussion around this recently. The consensus was that outgoing WebSocket connections prevented the DO from entering the "Idle, In-memory, & Hibernatable state" eventhough it's not listed as one of the three conditions that would do that in Lambros' awesome lifecycle diagram: https://developers.cloudflare.com/durable-objects/concepts/durable-object-lifecycle/. I don't think we ever got a definitive answer on that thread. Someone is going to have to run an experiment.

Cloudflare Docs

This section describes the lifecycle of a Durable Object.

Avi•8/20/25, 10:07 PM

super helpful diagram, thanks for pointing me to that! in our case, we are of course always in the 'idle' state

LarryOP•8/20/25, 10:24 PM

Huh? by sending every 100ms, you are toggling between the active and one of the two idle states, I believe?

LLarry Huh? by sending every 100ms, you are toggling between the active and one of the ...

Avi•8/20/25, 10:26 PM

no, it only enters idle+hibernateable after 10 seconds

Avi•8/20/25, 10:26 PM

that's why the hibernation API is useless for us

Avi•8/20/25, 10:27 PM

we never let the connection idle that long

Avi•8/20/25, 10:27 PM

in our case, we always remain in the active state

LarryOP•8/20/25, 10:30 PM

The 10-second delay is for going to "hibernated" not "hibernatable". It immediately goes to idle as soon as the message is done being sent or processed. Either of those should be well short of 100ms.

LLarry The 10-second delay is for going to "hibernated" not "hibernatable". It immediat...