{"version":"2.1.259","anchor":"ccr-client-can-hold-event-uploads-while-no-one-is-subscribed","canonical_anchor":"ccr-client-can-hold-event-uploads-while-no-one-is-subscribed","heading":"CCR client can hold event uploads while no one is subscribed","tier":"soon","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/ccr-client-can-hold-event-uploads-while-no-one-is-subscribed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### CCR client can hold event uploads while no one is subscribed\n\nEvent uploads can be held while a session has no subscribers, but the hold duration comes from a remote flag defaulting to zero.\n\nThe CCRClient's durable and internal event uploaders can now hold event uploads when a session has no subscribers. A new `noSubscriberUploadHoldMs` setting, set via `setNoSubscriberUploadHoldMs`, works with a `holdMaxItems: 50` cap on the internal-event uploader; releasing a hold logs telemetry event `ccr_no_subscriber_hold` with lane, reason, held_events, and held_ms. The hold duration comes from remote flag `tengu_ccr_no_subscriber_hold_ms` and defaults to 0 (also forced to 0 for outbound-only sessions), so the hold is inactive unless the server pushes a positive value.\n\n- Flag `tengu_ccr_no_subscriber_hold_ms`: Not enough to say (read for one account on one subscription tier against v2.1.259; this account: no value returned, anonymous baseline: no value returned, compiled default: no gate table built for this version) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Remote Control\n- Names: `noSubscriberUploadHoldMs`, `tengu_ccr_no_subscriber_hold_ms`, `setNoSubscriberUploadHoldMs`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}