{"version":"2.1.248","anchor":"the-worker-side-gains-matching-subscriber-aware-flush-state","canonical_anchor":"the-worker-side-gains-matching-subscriber-aware-flush-state","heading":"The worker side gains matching subscriber-aware flush state","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/the-worker-side-gains-matching-subscriber-aware-flush-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### The worker side gains matching subscriber-aware flush state\n\nWorkers can flush at a different pace when nobody is listening, and keep undelivered events.\n\n**What**\n\nThe 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.\n\n**Evidence**\n\n`noSubscriberStreamEventFlushIntervalMs`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}