The setting
runs a global network that developers and businesses use to build and protect applications. is a runtime that gives applications routing and storage and keeps their state, for uses such as real-time chat and multiplayer games.
The only snapshots that preserve some planning rooms also preserve information the customer requires deleted.
The CTO protects continuity for pilot participants, while the security executive requires removal of every restricted copy.
Who you’d be doing this for
“One department spent Friday setting up those rooms. Now I'm being asked which ones will still exist on Monday, and I don't have an answer.”
Fleur Reid · Customer Application Developer · a character in this brief
Maintains the planning application and must explain any lost pilot work to the people who created it.
What is at stake
A customer's 240 planning rooms contain restricted notes that must be deleted before launch. You must weigh irreversible removal against preserving room state when the only reconstruction copies also contain the notes.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- complete deletion vs continuity of pilot work
- selective cleanup vs provable coverage
- launch timing vs irreversible uncertainty
- shared diagnostics vs containment of restricted copies
Why Cloudflare
Workers event translation and R2 diagnostics put the customer's data boundary across both live session state and exported copies.
Written with these in mind
Not your kind of problem? 103 more at Cloudflare, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Cloudflare. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Senior Solutions Architect, APJC (Developer Platform) - India Market (opens in a new tab)
- Become recognized as a supportive, authoritative Developer Platform leader across APJC.
- Become a trusted technical advisor and collaborative partner to customers, partners, and internal leaders.
- Principal Solutions Architect, APJC (Developer Platform) - Mandarin Speaking (opens in a new tab)
- This is a senior, individual-contributor role that beautifully balances hands-on architecture, executive collaboration, regional technical leadership, and mentorship.
- Senior Customer Engineer- (AI & Start-Ups). Los Angeles (opens in a new tab)
- The role requires up to 25-30% travel to attend meetings with prospects or customers, attend conferences and other industry events, and to collaborate with your Cloudflare teammates.
- Customer Engineer AI/ Start Up's (opens in a new tab)
Reporting read before this brief was written
The pieces closest to the situation in this brief.
On October 2, 2026, celld, a runtime for running Cloudflare Workers and Durable Objects applications on one's own machines, described using deterministic simulation testing and found an alarm bug where a delayed cleanup removed a wake entry a new alarm still needed.
Deterministic simulation testing in celld: exploring execution orders and reproducing bugs · celld (opens in a new tab) · celld.dev · Oct 2, 2026
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.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about an irreversible change forced by a fixed date.
A halted filing draft cited a document removed 19 minutes earlier.
You must weigh uninterrupted legal research against a control that must be trusted before sensitive drafts proceed.
Agents have quoted 11 memories belonging to unrelated customers, and source conversations expire tonight.
You must weigh a broader permanent purge against retaining context whose ownership cannot all be checked in time.
Storage built for short-lived drafts cannot meet the contracted retention and retrieval terms at the volume coming.
Once you migrate the history in, reversing those boundaries and lifecycle rules gets expensive.
The same setting, from another role
Each is set around Cloudflare’s Durable Objects, written for a different role. They’re separate briefs, not the same scenario.
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.
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.
Overload errors are disconnecting players and leaving some match turns uncertain.
You must weigh immediate queue relief against the evidence needed to trust state recovery.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make a hard-to-reverse product decision feel clear and defensible before customers are bound by its consequences.
Deleted records now eat 31% of retention cost, and recovery is slowing in large bases before a fixed storage migration.
You have to cut the cost without removing data that customers expect to get back.
Routing differs by region, so time to the right owner varies threefold, and the slowest paths enter the next filing peak unchanged.
You decide what must be true before launch, since the new path is hard to undo.
A migration review found 14,600 old invoices the new service calculates differently, 430 with conflicting exemption evidence.
You decide what counts as correct before a switch you cannot undo.
