{"version":"2.1.311","anchor":"web-fetch-proxy-deadline-error-category","canonical_anchor":"web-fetch-proxy-deadline-error-category","heading":"Web fetch proxy timeouts now have their own error type","tier":"notice","area":"WebFetch","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/web-fetch-proxy-deadline-error-category","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Web fetch proxy timeouts now have their own error type\n\nWhen fetching a web page through a proxy runs out of time, Claude Code now reports it as its own kind of error\n\n**What**\n\nWhen Claude Code fetches a web page through a proxy (a go-between server) and the request runs out of time, the error is now reported under its own category, `web_fetch_proxy_deadline`. It sits alongside the existing categories for connection problems and bad responses.\n\n**Why**\n\nProxy timeouts can now be told apart from other web fetch failures.\n\n- Area: WebFetch\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}