{"version":"2.1.248","anchor":"the-no-subscriber-flush-interval-is-inert-at-its-default-of-","canonical_anchor":"the-no-subscriber-flush-interval-is-inert-at-its-default-of-","heading":"The no-subscriber flush interval is inert at its default of 0","tier":"soon","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/the-no-subscriber-flush-interval-is-inert-at-its-default-of-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### The no-subscriber flush interval is inert at its default of 0\n\nSubscriber-aware flush buffering is disabled by its default of zero.\n\n**What**\n\nThe subscriber-aware buffering above is switched off in this build. The interval comes from `tengu_ccr_no_subscriber_flush_ms` with a fallback of 0, and 0 disables the path entirely, so only a server value can turn it on.\n\n**Details**\n\n- The server's events response carries a `has_subscribers` field, but the response body is only parsed at all when the interval is greater than 0.\n- The value is re-read on every remote-config refresh, so it can start applying mid-session without a restart.\n- With it enabled, ephemeral events wait for the longer of the two intervals instead of the normal one, meaning a cloud session nobody is watching streams less eagerly.\n\n**Evidence**\n\n`tengu_ccr_no_subscriber_flush_ms`\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: Remote Control\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}