Not switched on
Useful1 Signal4
Remote bridge shutdown waits for its disconnect notice, and a new inbox fetch always refuses.
A message-fetch entry point exists but is hard-disabled, returning feature_disabled every time.
What's wrong with this entry?
Anonymous. No account, no email.
What
Bridge teardown now waits for the pending disconnect notice on both the normal and skip-archive exits. A new message-fetch entry point is present but hard-disabled: it always returns a failure with the reason feature_disabled.
Details
- The polling client marks the worker generation as superseded before every fatal generation mismatch: repeated 404s, an expired session token, and exhausted authentication failures. That lets shutdown tell a replaced session apart from a live one.
- The flush is exposed on the transport alongside close.
Evidence
feature_disabled
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.
-
v2.1.234
Remote bridge replaces stale-epoch recovery with a one-shot supersession close
Both mention bridge
-
v2.1.238
Three new remote bridge flags for auth recovery and session end
Both mention bridge
-
v2.1.238
Remote inbox fetching is instrumented but has no working path
Both mention bridge