The archive cutover must protect a contract deadline and prove that downstream retrieval is trustworthy.
Customer engineering wants to leave a changing self-hosted estate, while risk will not approve a production write path with unresolved retrieval evidence.
Who you’d be doing this for
“The object is in the bucket, then the job says it is missing and I’m the one answering for it.”
Nazir Kurniawan · Staff Backend Engineer
Owns the customer service that retrieves archived media for downstream processing.
What is at stake
Some archived files appear in R2 while downstream jobs still receive missing-object responses. You must weigh a time-bound cutover against evidence that the production retrieval path is safe to trust.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- contract deadline vs retrieval confidence
- self-hosted continuity vs platform migration
- production speed vs reviewed evidence
- customer-specific workaround vs reusable product insight
Why Cloudflare
R2 and Workers sit directly in the customer’s new archive path, so an unproven handoff between storage and processing determines whether the platform becomes operational infrastructure.
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.