{"version":"2.1.248","anchor":"cloud-sessions-batch-stream-events-and-hold-them-back-when-n","canonical_anchor":"cloud-sessions-batch-stream-events-and-hold-them-back-when-n","heading":"Cloud sessions batch stream events and hold them back when nobody is watching","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/cloud-sessions-batch-stream-events-and-hold-them-back-when-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Cloud sessions batch stream events and hold them back when nobody is watching\n\nCloud sessions batch stream events and can hold them back when nobody is watching.\n\n**What**\n\nThe client that ships events for remote and cloud sessions gained a batch upload path and an awareness of whether anyone is subscribed to the stream. When the last server report said there were no subscribers, ephemeral stream events are buffered for the longer of the no-subscriber interval and the normal flush interval, and flushed immediately once a subscriber shows up. The extra delay comes from `tengu_ccr_no_subscriber_flush_ms`, default 0, which disables it.\n\n**Details**\n\n- Single-event writes now go through the batch path.\n- Values are clamped to 0 through 60000; a non-finite value is logged and ignored.\n- Delivery reports of \"received\" mark subscribers as present, ending the delay early.\n- Consecutive `thinking_tokens` system events in the buffer are merged, summing their estimated token deltas.\n\n**Evidence**\n\n`setNoSubscriberStreamEventFlushIntervalMs`\n\n- Flag `tengu_ccr_no_subscriber_flush_ms`: Not enough to say (read for one account on one subscription tier against v2.1.248; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read)\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}