{"version":"2.1.223","anchor":"ccr-stream-event-flush-interval-is-validated-and-clamped","canonical_anchor":"ccr-stream-event-flush-interval-is-validated-and-clamped","heading":"CCR stream-event flush interval is validated and clamped","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/ccr-stream-event-flush-interval-is-validated-and-clamped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### CCR stream-event flush interval is validated and clamped\n\nA remotely tuned batching interval is now range-checked so a bad value cannot break event flushing.\n\n**What**\n\nThe flush interval for CCR client stream events is now sanity-checked instead of being used as supplied.\n\n**Details**\n\n- The value comes from the remote config `tengu_ccr_stream_event_flush_ms`, falling back to a built-in default.\n- String values are coerced to numbers.\n- Non-finite values produce a warning and fall back to the default.\n- The final value is clamped to 0 to 60000 ms.\n\n**Evidence**\n\n`CCRClient: non-finite streamEventFlushIntervalMs`\n\n- Flag `tengu_ccr_stream_event_flush_ms`: Not enough to say (read for one account on one subscription tier against v2.1.223; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}