If the server forgets your session registration, remote control now re-registers and resumes.
What's wrong with this entry?
If the remote control connection closes with code 4090, meaning the session's registration on the server went stale, the client now re-registers and resumes instead of treating the session as lost.
- Shown during reconnect as "session registration went stale — re-registering".
- Recorded with cause
epoch_staleand, on success, recovery coderecovered_epoch_stale. - Teardown no longer routes this close code down the abandoned-recovery path.
session registration went stale \u2014 re-registering
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.