{"version":"2.1.299","anchor":"ccr-upload-retries-in-smaller-batches-after-no-response","canonical_anchor":"ccr-upload-retries-in-smaller-batches-after-no-response","heading":"Remote sessions retry uploads in smaller batches when the server does not answer","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/ccr-upload-retries-in-smaller-batches-after-no-response","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Remote sessions retry uploads in smaller batches when the server does not answer\n\nIn remote sessions, an upload that gets no response is now retried in smaller and smaller batches instead of resent whole\n\n**What**\n\nIn remote sessions, Claude Code sends batches of events to a server. When one of those uploads gets no response, it now retries in smaller batches, halving the size each time down to a minimum, and logs a warning. Before, the batch was put back in the queue whole.\n\nRegular check-in messages also now prompt the connection to resync when its access token is close to expiring.\n\n**Why**\n\nRemote sessions should cope better with uploads that hang, rather than repeatedly resending the same large batch.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}