ship review · offline editing
Finish the ship review
The resend is accepted for the first patch: it recovered all 500 forced stalls,
and a six-week beta across 96 workspaces saw no data loss. One decision remains.
Finish choosing the follow-up work in the reconnect thread, then approve version
1 of this review.
Confirm the follow-up work
Open the comment beside the stalled task. Two follow-ups are selected; adjust
them if needed, then press Done.
Ship offline editing in the first patch
iOS reconnect stall One reconnect in about 40. Nothing is
lost — the edits stay queued — but the reader sees a spinner until they
background the app.
Keep the resend workaround in the patch After 20 seconds
the client resends the queued batch; 500 forced stalls all recovered.
Patch decision: ship with the resend
Ship with the resend and keep chasing the upstream fix.
Hold the patch for a native fix.
Land the upstream fix The vendor reproduced the stall but
has not named a release.
Keep reconnect telemetry The beta alert and per-platform
count remain on for the release cohort.
Write the support playbook It covers the spinner, queued
edits, and background-app recovery.
- Observed
- 1 reconnect in about 40
- Data loss
- none in 8,412 offline sessions
- Workaround
- resend after 20 seconds
- Upstream fix
- acknowledged, no release date