Unclear Whether this feature is active for any given account depends on the tengu_ccr_event_hold_enabled gate, which is unread for this account, so nothing can be said about whether it is switched on. It's also unclear what effect enabling the hold has in practice.
What
- A new
eventHoldEnabledflag (on by default) enables holding of served-policy events, and a newdropUnwatchedStreamEventsflag (off by default) drops stream events entirely when no subscriber is watching them. Both are wired into the CCR (client-cloud relay) worker config. - The CCR client now passes
dropUnwatchedStreamEventsat construction, and this can be toggled live via a GrowthBook-refresh subscription that callssetDropUnwatchedStreamEvents. - The CCR client also gains an
eventHoldEnabledcallback option, backed by a GrowthBook flag.
Why These flags give more control over event traffic in remote/CCR sessions, reducing unnecessary event delivery when nothing is subscribed and allowing event-holding behavior to be toggled remotely without a client update.
tengu_ccr_event_hold_enabled 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.268: on
Read once, for one account on one subscription tier, against v2.1.268. It isn't a statement about your account. What a flag value here can and cannot tell you
Whether this feature is active for any given account depends on the tengu_ccr_event_hold_enabled gate, which is unread for this account, so…
New in this build: tengu_ccr_event_hold_enabled