- Shipped
- August 25, 2026 at 4:04 PM UTC
- Author
- Kamo
- Commit
- 1a7791c
session_durable treated a REJECTED token as a durability failure. That is not the outage it guards: a gateway restart, or Guacamole's own inactivity timeout, invalidates the token outright, so every legitimate deploy would have raised KamoDesktopReconnectsBroken for up to an hour afterwards. An alert that cries wolf after each deploy is how a real one gets ignored — and this canary exists because a real one already was. The outage signature is narrower and is still caught unchanged: a token that is ACCEPTED but whose connection directory has silently gone empty. A rejected token now retires the held session and adopts a fresh one, so the guard keeps working from that cycle on rather than staying stuck on a dead token.