Under the hood
Useful1 Signal2
When a background bridge worker can't get your login token, it now records exactly why.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a bridge worker knows which account it is for but cannot get a token, it now classifies the reason and reports it, distinguishing signed out, a dead refresh token, an unreadable credential store, an identity present with no usable token, and timeout or error cases.
Details
- Reported as
tengu_bridge_token_absence_classified; a dead refresh token is a stored value that is the empty string. - Only fires when the token came from the credential store and an account identifier is cached.
- The expired-login prompt now keys off the same dead-refresh-token probe instead of its previous check.
Evidence
tengu_bridge_token_absence_classified
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.222
Bridge recovery has a rebuild budget and richer failure telemetry
Both mention bridge
-
v2.1.224
Two new remote-config gates for bridge event forwarding
Both mention bridge
-
v2.1.234
Remote bridge replaces stale-epoch recovery with a one-shot supersession close
Both mention bridge