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. Approve the release with that workaround below, and choose the follow-up work separately in the reconnect thread.
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
review · mobile
- iOS reconnect stall stalled · mobile One reconnect in about 40. Nothing is lost — the edits stay queued — but the user sees a spinner until they background the app.
-
Keep the resend workaround in the patch
review · mobile 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 blocked · mobile The vendor reproduced the stall but has not named a release.
- Keep reconnect telemetry done · data The beta alert and per-platform count remain on for the release cohort.
- Write the support playbook done · support 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
Ship the iOS patch with the resend workaround?
The first patch would carry automatic resend after 20 seconds, reconnect telemetry and the support playbook described above. The upstream fix and additional reconnect work remain follow-ups.