{"version":"2.1.311","anchor":"ccr-joint-upload-pauses-itself-after-route-failures","canonical_anchor":"ccr-joint-upload-pauses-itself-after-route-failures","heading":"Cloud session uploads pause and retry when the server can't take them","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/ccr-joint-upload-pauses-itself-after-route-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Cloud session uploads pause and retry when the server can't take them\n\nCloud session uploads now pause with growing waits after repeated route failures, or at once on a 405 or 501 response\n\n**What**\n\nIn a cloud session, Claude Code sends the session's events up to a server. That uploader now backs off when the server does not support the way it sends them. It pauses uploading:\n\n- after two failures caused by the route being unavailable\n\n- straight away on a 405 or 501 response, which are server replies meaning the request type is not supported\n\nWhile paused, it waits longer each time before trying again, and logs a warning.\n\n**Why**\n\nAgainst a server that does not support this kind of upload, Claude Code no longer keeps hammering it with requests that will fail.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}