{"version":"2.1.232","anchor":"gateway-settings-failures-now-say-what-actually-went-wrong","canonical_anchor":"gateway-settings-failures-now-say-what-actually-went-wrong","heading":"Gateway settings failures now say what actually went wrong","tier":"notice","area":"Cloud Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/gateway-settings-failures-now-say-what-actually-went-wrong","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Gateway settings failures now say what actually went wrong\n\nGateway settings failures now name the exact cause, from TLS mismatch to a rejected credential.\n\n**What**\n\nWhen Claude Code cannot fetch managed settings from a Cloud gateway, it now shows a specific reason rather than a generic failure. Wording covers \"couldn't connect to the gateway\", \"the gateway did not accept this session's credential\", \"no credential was on hand for the request\", \"the gateway's response was not valid managed settings\", \"the gateway's TLS certificate did not match the one you trusted\", and \"something unexpected went wrong (details with --debug)\".\n\n**Details**\n\n- The fetch returns a failure record carrying the error kind, the HTTP status, and whether the gateway's certificate pin mismatched, instead of a plain success\/failure boolean.\n- A certificate pin mismatch on the first request after login produces its own message beginning \"Cloud gateway sign-in was not completed:\" and the new credentials are discarded.\n\n**Evidence**\n\n`the gateway's response was not valid managed settings`\n\n- Area: Cloud Gateway\n- Names: `--debug`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}