{"version":"2.1.290","anchor":"fetch-failures-now-record-headers-timeout","canonical_anchor":"fetch-failures-now-record-headers-timeout","heading":"Network request failures now record when the server's reply timed out","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/fetch-failures-now-record-headers-timeout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Network request failures now record when the server's reply timed out\n\nFailed network requests now record whether the server took too long to start replying, which the old code stored in the wrong place\n\n**What**\n\nWhen a network request fails, Claude Code now records whether it failed because the server took too long to send the start of its reply, known as the headers. The old code saved failure details in the wrong place.\n\n**Why**\n\nFailures caused by a slow server reply can now be told apart from other failures.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}