{"version":"2.1.285","anchor":"prefetch-failures-now-count-as-non-retryable-unless-bytes-we","canonical_anchor":"prefetch-failures-now-count-as-non-retryable-unless-bytes-we","heading":"Changed rule for which failed downloads are counted","tier":"internal","area":"Attachments","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/prefetch-failures-now-count-as-non-retryable-unless-bytes-we","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Changed rule for which failed downloads are counted\n\nA failed download that was not a prefetch now always counts; a prefetch counts only if data arrived or it was too large\n\n**Unclear.** What this check feeds into, including whether a counted failure means the download is not retried, is not clear.\n\n**What**\n\nClaude Code changed the rule it uses to decide whether a failed download counts. A prefetch is a download started ahead of time, before anything asked for it.\n\n- Downloads that were not a prefetch: any failure now counts. Before, a failure counted only if some data had arrived, the file was too large, or the download stalled.\n\n- Prefetch downloads: a failure counts only if some data had arrived or the file was too large. This is unchanged.\n\n**Why**\n\nFailed downloads that were started on demand are now treated more strictly than before, since every such failure counts rather than only certain kinds.\n\n- Area: Attachments\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}