[Bug]: Settle and snooze fail on threads from an offline machine instead of applying locally and syncing on reconnect#24532
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/mobile
Steps to reproduce
This is the remaining part of #4852, opened as a separate issue as the closing comment there asked.
Setup: a Mac and a Windows PC running T3 Code, and the mobile app paired to both.
- Have some threads on the Mac that need attention.
- Shut down the Mac (or close T3 Code on it).
- On the phone, try to settle or snooze one of the Mac's threads.
Expected behavior
Settle and snooze apply on the phone right away. The thread is marked as waiting to sync, and the change is sent to the Mac when it reconnects. If the Mac changed the thread in the meantime, the Mac's state wins and the phone shows that.
These are triage actions on my own list. They shouldn't need the machine that ran the thread to be online.
Actual behavior
Both fail with " is not connected." The threads stay in the list until the Mac is back on, and combined with #24530 they show stale state the whole time.
Impact
Major degradation or frequent failure
Version or commit
Desktop: 0.1.3-nightly.20261023.3592. Mobile: current release.
Environment
macOS + Windows 11 desktops, mobile app paired to both.
Workaround
Turn the Mac back on, then settle or snooze.
Related: #4852 (closed; this is the part still open), #24530 (stale state shown as current), Ideas #24529.