Google credential failures buried inside another error are now identified properly.
What's wrong with this entry?
Google 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.
- Matched messages include
Could not load the default credentials,Could not refresh access tokenandinvalid_grant, plus one further substring. - The top-level value no longer has to be an
Errorinstance for the check to fire.
Could not refresh access token
Strings lifted out of the shipped bundle, so the claim above can be checked against them.