Overload investigations need speed without turning a plausible explanation into a production change.
The evidence trail must shorten triage while engineers preserve the correctness bar for routing, storage, and runtime changes.
Who you’d be doing this for
“Our busiest rooms are the ones people notice, and I’m refreshing logs while users ask why turns stopped landing.”
Nkechi Babajide · Application Developer
Builds a real-time application whose session state is coordinated through Durable Objects.
What is at stake
Busy Durable Objects can slow down or reject turns while adjacent objects remain healthy. You must decide what evidence AI can assemble and what an engineer must verify before a fix moves forward.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- faster triage vs. causal certainty
- ranked hypotheses vs. engineer accountability
- reusable patterns vs. incident-specific context
- runtime safety vs. investigation speed
Why Cloudflare
Durable Objects depend on low-level routing and storage systems that must keep live application state reliable under concentrated load.
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.