Verify without starting over
Routine freshness checks previously used the same teardown path as account transitions. Even a successful response for the same user could close Sentry and reset workspace state. Watchtower now verifies unchanged identity and permissions in place, coalesces simultaneous checks and updates expiry or display metadata without treating it as a new account.
Short interruptions and real boundaries
A brief transient status failure gets one retry within the existing bounded verification window. Confirmed logout, expiry, owner changes and permission changes still use the strict cleanup path. An exhausted or invalid verification pauses private access and uses the existing recovery flow. Session lifetimes and server-side authorization are not extended or bypassed.
Verified continuity
Desktop/mobile checks cover delayed successful verification, shared requests, transient retry, expiry, revocation, account switching, cross-tab logout, late responses and untrusted cached labels. A real Sentry conversation stayed connected through routine checks and a transient retry, then stopped when its isolated test account was disabled.
Load the update
Refresh Watchtower once to load the new session lifecycle. Subsequent routine checks should preserve your active workspace when the server confirms the same account and permissions. Genuine expiry or access changes can still require signing in again.