{"version":"2.1.283","anchor":"file-uploads-fail-fast-on-400404422-and-non-retried-timeou","canonical_anchor":"file-uploads-fail-fast-on-400404422-and-non-retried-timeou","heading":"File uploads stop retrying when the server rejects them outright","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/file-uploads-fail-fast-on-400404422-and-non-retried-timeou","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### File uploads stop retrying when the server rejects them outright\n\nFile uploads now fail at once on HTTP 400, 404 or 422, and on timeouts set not to retry, instead of retrying\n\n**What**\n\nWhen Claude Code uploads a file, some failures now end the upload at once instead of retrying:\n\n- HTTP 400, 404 or 422 from the server, meaning the server rejected or could not find what was sent, is reported as a server error.\n\n- A timeout on an upload set not to retry after timeouts is reported as a network error.\n\nBefore, other error codes went down the retry path, and every connection error was simply tried again.\n\n**Why**\n\nUploads that can never succeed no longer keep retrying, so the failure shows up sooner.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}