Session recovery needs durable ordering without forcing every application to invent its own protocol.
Reconnect speed protects live interaction, while replay safety protects the state each session already committed.
Who you’d be doing this for
“A customer asked why their edit showed up twice, and I had to trace every retry by hand.”
Moira Clarke · Staff Application Developer
Builds collaborative application sessions on Durable Objects and is accountable for keeping participant state consistent after reconnects.
What is at stake
Developers are replaying uncertain events after disconnects, which can duplicate or lose session state. You have to weigh a simple recovery API against the runtime guarantees needed to make it trustworthy.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- reconnect speed vs durable ordering
- small API surface vs useful recovery guarantees
- runtime simplicity vs application-level replay burden
- feature adoption vs storage overhead
Why Cloudflare
Durable Objects carries the session state behind chat, multiplayer, and agent workloads that depend on ordered recovery at the edge.
Written with these in mind
Not your kind of problem? 51 more at Cloudflare, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.