{"version":"2.1.281","anchor":"api-credential-validation-distinguishes-auth-failures-from-r","canonical_anchor":"api-credential-validation-distinguishes-auth-failures-from-r","heading":"API credential validation distinguishes auth failures from retryable network errors","tier":"notice","area":"Auth","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/api-credential-validation-distinguishes-auth-failures-from-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### API credential validation distinguishes auth failures from retryable network errors\n\nChecking your API credentials now tells a rejected login apart from a network error worth retrying\n\n**What**\n\nWhen Claude Code checks your API credentials, the result now says which kind of failure happened:\n\n- `authFailed` when the credentials themselves were rejected\n\n- `retryable` for network errors, such as \"Network error. Please check your internet connection.\"\n\n**Why**\n\nA bad connection and a bad key are now reported as different problems, so a network glitch can be treated as something to try again rather than as wrong credentials.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}