Subscriber-aware flush buffering is disabled by its default of zero.
tengu_ccr_no_subscriber_flush_ms defaults to 0, which disables the path.
tengu_ccr_no_subscriber_flush_ms Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.248: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The 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.
- The server's events response carries a
has_subscribersfield, but the response body is only parsed at all when the interval is greater than 0. - The value is re-read on every remote-config refresh, so it can start applying mid-session without a restart.
- 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.
tengu_ccr_no_subscriber_flush_ms
Strings lifted out of the shipped bundle, so the claim above can be checked against them.