{"version":"2.1.323","anchor":"attachment-download-honours-retry-after","canonical_anchor":"attachment-download-honours-retry-after","heading":"Attachment downloads wait as long as the server asks before retrying","tier":"notice","area":"File Attachments","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/attachment-download-honours-retry-after","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Attachment downloads wait as long as the server asks before retrying\n\nWhen an attachment download is rate-limited or the service is busy, Claude Code now waits the time the server asks, up to a limit\n\n**What**\n\nWhen Claude Code downloads an attachment and the server answers that too many requests are coming in (status 429) or that it is temporarily unavailable (status 503), Claude Code now reads the server's `Retry-After` header. That header says how long to wait. Claude Code uses that wait before trying again, capped at a maximum. Before, it only used its own waits, which grew longer with each attempt.\n\nThe timing details Claude Code reports about downloads now also count retries and failures.\n\n**Why**\n\nRetries are gentler on a server that is already overloaded, so downloads are more likely to succeed instead of failing again straight away.\n\n- Area: File Attachments\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}