{"version":"2.1.285","anchor":"attachment-prefetch-is-gated-by-a-flag-and-the-download-pat","canonical_anchor":"attachment-prefetch-is-gated-by-a-flag-and-the-download-pat","heading":"Attachment downloads retry on failures, and early fetching can be switched off","tier":"notice","area":"Attachments","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/attachment-prefetch-is-gated-by-a-flag-and-the-download-pat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Attachment downloads retry on failures, and early fetching can be switched off\n\nAttachment downloads now retry after stalls and some server errors, and fetching attachments ahead of time can be turned off by a setting\n\n**Unclear.** The name of the setting that controls early fetching, and whether it is on by default, are not known.\n\n**What**\n\nClaude Code can fetch attachments ahead of time, before they are needed. This early fetching now stops straight away when a setting reads as off.\n\nAttachment downloads now retry, waiting a little longer each time, when the download stalls or the server answers with a 5xx error, 408 (request timeout) or 429 (too many requests). Previously there was no retry. The timing record kept for each download also counts inline images and failures.\n\n**Why**\n\nWhether early fetching is on affects how quickly attachments arrive, and the retries let a download recover from a brief stall or server hiccup instead of failing.\n\n- Area: Attachments\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}