{"version":"2.1.238","anchor":"bridge-workers-report-why-they-had-no-login-token","canonical_anchor":"bridge-workers-report-why-they-had-no-login-token","heading":"Bridge workers report why they had no login token","tier":"internal","area":"Remote Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/bridge-workers-report-why-they-had-no-login-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Bridge workers report why they had no login token\n\nWhen a background bridge worker can't get your login token, it now records exactly why.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- Reported as `tengu_bridge_token_absence_classified`; a dead refresh token is a stored value that is the empty string.\n- Only fires when the token came from the credential store and an account identifier is cached.\n- The expired-login prompt now keys off the same dead-refresh-token probe instead of its previous check.\n\n**Evidence**\n\n`tengu_bridge_token_absence_classified`\n\n- Area: Remote Bridge\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}