GUIDES · BETSLIP DOCTOR
What happens to a pending read when I leave a BSD screen or my account session changes?
A pending navigation metadata read is checked against the screen's current scope before and after loading. Leaving that scope can retire the read, and the authenticated client also checks that its session is still current before accepting a response. This protects the new view from a late answer, but it does not undo a server-side write or promise that every request automatically restarts.
For BSD readers who leave a screen or change accounts while information is loading · Updated
A pending read belongs to its current screen scope
The recorded navigation read cache keys metadata by the account owner and navigation generation. It checks that scope before and after the read. If the consumer leaves or the scope is no longer current, the old result is not accepted as the answer for a different screen.
When no consumer remains for a fetching entry, the cache can cancel and remove that query. A later screen can make its own current read; the source does not promise that every canceled request automatically restarts.
A session change also retires the old response
The product client captures an authenticated session lease, listens for its abort signal, and checks that the lease is still current around the request. A response from an old account session therefore cannot be treated as a fresh read for the new session.
This is a read boundary. Navigation or session cancellation does not roll back a write that the server already completed, and these source anchors do not establish automatic replay of all pending work. Check the current screen and account before acting on a result.
Hypothetical: leaving a screen during a read
Imagine a reader opens a BSD screen while its metadata is loading, then leaves and signs into another account. The old navigation scope is no longer current, so its late response is not used as the new account's answer. This example concerns a read; it does not claim that a completed save was undone.
Related questions
Does leaving a screen undo a request that already saved something?
No such rollback is established by the navigation read-cache source. It describes retiring reads, not undoing a server-side write that has already completed.
Will every canceled read restart automatically?
The source does not promise that. A current screen may make a new read, but a canceled or retired request should not be treated as a guaranteed automatic restart.