{"version":"2.1.250","anchor":"cloudflare-and-load-shed-disconnects-are-recognised-and-repo","canonical_anchor":"cloudflare-and-load-shed-disconnects-are-recognised-and-repo","heading":"Cloudflare and load-shed disconnects are recognised and reported","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.250\/e\/cloudflare-and-load-shed-disconnects-are-recognised-and-repo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.250","markdown":"### Cloudflare and load-shed disconnects are recognised and reported\n\nClaude Code can now tell when a watch was cut off by traffic protection or server overload rather than a real error.\n\n**What**\n\nConnection close reasons of the form `cf_mitigated_<status>` or `upgrade_rejected_<status>` are now decoded back into an HTTP status and a Cloudflare flag. The previous build only wrote those strings. A close counts as a load shed when the status is 5xx, 429 or 408, or when Cloudflare mitigated it.\n\n**Details**\n\n- Failure telemetry now carries `shed`, `http_status` and `cf_mitigated` fields; before it could only report a fixed stalled marker.\n- A shed close is folded into the stalled decision and no longer clears the cached token lease.\n\n**Evidence**\n\n`cf_mitigated`, `\/^(cf_mitigated|upgrade_rejected)_(\\d{1,3})$\/`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}