{"version":"2.1.246","anchor":"saved-oauth-tokens-are-pushed-into-the-storage-backed-creden","canonical_anchor":"saved-oauth-tokens-are-pushed-into-the-storage-backed-creden","heading":"Saved OAuth tokens are pushed into the storage-backed credential cache","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/saved-oauth-tokens-are-pushed-into-the-storage-backed-creden","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Saved OAuth tokens are pushed into the storage-backed credential cache\n\nSaved login tokens now propagate into the newer storage-backed credential cache.\n\n**What**\n\nAfter either token-save path writes, it now clears the in-process caches and waits for the new value to propagate into the version 5 storage handle when that handle exists, passing along whatever was cached before.\n\n**Details**\n\n- A related helper was cut down to a cache reset plus a conditional refresh.\n- Only the storage version 5 path does the propagation step.\n\n**Evidence**\n\n`tengu_oauth_tokens_saved`\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}