{"version":"2.1.281","anchor":"ccr-upload-hold-reasons-link-held-and-turn-held","canonical_anchor":"ccr-upload-hold-reasons-link-held-and-turn-held","heading":"Cloud session sync gains held and deferred outcomes","tier":"internal","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/ccr-upload-hold-reasons-link-held-and-turn-held","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud session sync gains held and deferred outcomes\n\nCloud session sync can now report uploads as held or deferred, and failed journal writes stop retrying after a limit\n\n**Unclear.** The finding does not say what CCR is or what causes an upload to be held.\n\n**What**\n\nWhen Claude Code syncs a session to the cloud, each upload ends with an outcome that records what happened to it. This release adds new outcomes that mark an upload as waiting rather than done or failed:\n\n- `link_held`, recorded as deferred because it is `awaiting_container`\n\n- `turn_held`, recorded as deferred until `turn_end`, the end of the current turn\n\n- `link_pending`\n\n- `deferred_head_unreadable`\n\nA `journal_failed` outcome now settles after a limited number of retries. Before, it retried every time.\n\n**Why**\n\nA sync that cannot go ahead yet is now marked as waiting instead of failed, and a failure that keeps repeating no longer retries forever.\n\n- Area: Cloud Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}