{"version":"2.1.227","anchor":"more-cloud-token-failures-recognised-as-expired-credentials","canonical_anchor":"more-cloud-token-failures-recognised-as-expired-credentials","heading":"More cloud token failures recognised as expired credentials","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/more-cloud-token-failures-recognised-as-expired-credentials","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### More cloud token failures recognised as expired credentials\n\nMore Bedrock and Vertex token failures now say your credentials expired so you can re-authenticate.\n\n**What**\n\nThree more provider error strings are now matched by the check that classifies a failure as expired or invalid credentials, so Bedrock and Vertex style token and API key failures surface as an auth expiry you can re-authenticate from, instead of a generic error.\n\n**Evidence**\n\n`Bearer Token has expired`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}