{"version":"2.1.228","anchor":"google-credential-failures-recognised-when-wrapped-in-anothe","canonical_anchor":"google-credential-failures-recognised-when-wrapped-in-anothe","heading":"Google credential failures recognised when wrapped in another error","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/google-credential-failures-recognised-when-wrapped-in-anothe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Google credential failures recognised when wrapped in another error\n\nGoogle credential failures buried inside another error are now identified properly.\n\n**What**\n\nGoogle authentication failures are now detected by walking the chain of nested causes rather than only inspecting the top-level error, so a wrapped credential failure is classified correctly instead of surfacing as a generic error. One more matching message was added to the existing set.\n\n**Details**\n\n- Matched messages include `Could not load the default credentials`, `Could not refresh access token` and `invalid_grant`, plus one further substring.\n- The top-level value no longer has to be an `Error` instance for the check to fire.\n\n**Evidence**\n\n`Could not refresh access token`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}