{"version":"2.1.261","anchor":"gcp-credential-auth-refresh-check-gains-timeout-handling","canonical_anchor":"gcp-credential-auth-refresh-check-gains-timeout-handling","heading":"GCP credential auth-refresh check gains timeout handling","tier":"notice","area":"Cloud Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/gcp-credential-auth-refresh-check-gains-timeout-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### GCP credential auth-refresh check gains timeout handling\n\nA slow GCP credential check no longer forces an unnecessary refresh; it waits for an actual rejection.\n\nThe GCP credentials validity check used before running the auth refresh command now distinguishes a timeout from an actual valid\/invalid result. If the check times out, the refresh command is skipped and a log message notes it's deferring until the API actually rejects the credentials, instead of always re-running the refresh command on any failure or exception as before. If the API had already rejected the credentials before the timeout, the refresh still runs.\n\n- Area: Cloud Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}