{"version":"2.1.228","anchor":"credential-refresh-failures-are-now-distinguishable","canonical_anchor":"credential-refresh-failures-are-now-distinguishable","heading":"Credential refresh failures are now distinguishable","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/credential-refresh-failures-are-now-distinguishable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Credential refresh failures are now distinguishable\n\nCredential refresh failures now report which specific thing went wrong instead of just failing.\n\n**What**\n\nRefreshing host credentials throws with a distinct error for each failure mode: the credential file failing to re-read, an endpoint variable changing between reads, and a refresh that came back without the bearer key. All three previously returned null.\n\n**Evidence**\n\n`host-creds refresh dropped the bearer key`\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}