Under the hood
Useful2 Signal3
Workers can flush at a different pace when nobody is listening, and keep undelivered events.
What's wrong with this entry?
Anonymous. No account, no email.
What
The worker process now tracks the no-subscriber flush interval, the last reported subscriber state and the reports themselves alongside its existing stream-event buffer and timer, so its flush cadence can differ when nobody is listening. Closing a connection can also now retain undelivered client events rather than dropping them.
Evidence
noSubscriberStreamEventFlushIntervalMs
Strings lifted out of the shipped bundle, so the claim above can be checked against them.