{"version":"2.1.311","anchor":"prefetch-failure-retry-logic-changed","canonical_anchor":"prefetch-failure-retry-logic-changed","heading":"Change to how a too-large download failure is judged","tier":"internal","area":"Network","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/prefetch-failure-retry-logic-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Change to how a too-large download failure is judged\n\nA download that fails for being too large no longer always counts the same way; Claude Code now runs an extra check first\n\n**Unclear.** It is not known what data is being fetched ahead of time.\n\n**What**\n\nClaude Code fetches some data ahead of time, before it is needed. It then checks whether a failed fetch should count as a failure worth acting on. A fetch that fails because the data was too large used to count every time. Claude Code now runs an extra check in that case and decides from the result. When there is no failure at all, the check now plainly reports no failure.\n\n**Why**\n\nThis changes when a failed download is treated as worth trying again.\n\n- Area: Network\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}