[Bug]: Snoozed threads dissapeared (auto-settled?)

[bzbetty]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

Running the nightly (although woudl have been 4ish days old)

Couple of days ago I had 8+ snoozed threads, today I had none. My suspicion is that they woke up (believe they were due to wake yesterday) and were auto settled within a minute due to inactivity.

I thought I had the auto settle on activity setting turned off, however when i checked settings it was on. unsure if I was mistaken or somethign enabled it again.

Given the number of threads I do in a day it's hard to search through the settled ones to verify if they're there.

Expected behavior

• Auto-settle setting shouldn't turn back on if I have it off
• Threads that wake need a decent grace period before they're auto-settled (maybe reset their timer?)

Actual behavior

• snoozed threads missing when I look for them

Impact

Major degradation or frequent failure

Version or commit

No response

Environment

Windows

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

[juliusmarminge]

Triage

Confirmed as a real settlement-policy bug, not a desktop-only hide and not a duplicate of #6368.

Snooze wake is derived: when snoozedUntil passes, no server event fires and no activity timestamp is updated (packages/client-runtime/src/state/threadSettled.ts). The settlement reactor then treats the thread as a normal inactivity candidate (apps/server/src/orchestration/ThreadSettlementPolicy.ts) and sweeps about once a minute (ThreadSettlementReactor). Inactivity is measured from last user/turn activity only — not from wake. Default window is 3 days. Settling also unsnoozes the thread, so the row leaves Snoozed and lands in Settled.

That matches “they woke yesterday and were gone within a minute.” It also hits Next week snoozes, or any thread already idle ≥ 3 days before snooze. A still-snoozed thread can even settle early if a run completed after snooze and then sat past the window (covered by an existing policy test).

No open/merged PR resets the inactivity clock on wake. Adjacent items: #6368 / #7179 (completion waking snooze — different), #5377 / #5379 (settle clears snooze), #9903 (stale failures vs settlement eligibility). Discussions #11210, #11399, #6833 are feature ideas.

Auto-settle toggle flipping back on: no silent null → 3 write path found; null persists. Default is on (3 days). More likely: misremembered default, mix-up with Auto-settle merged threads, project vs environment scope, shared-settings / reset-to-defaults, or a settings.json decode fallback. Not blocking the wake-timer fix.

Workaround: look under Settled and Un-settle. Turn off Settings → General → Auto-settle inactive threads (or raise the day count) if you do not want this.

Fix: treat wake (snoozedUntil / early-wake time) as the inactivity anchor, or grant a grace period after wake, so a just-woke thread is not settled because pre-snooze work is old.