{"version":"2.1.268","anchor":"ccr-heartbeat-can-adopt-a-server-pushed-event-flush-policy","canonical_anchor":"ccr-heartbeat-can-adopt-a-server-pushed-event-flush-policy","heading":"CCR heartbeat can adopt a server-pushed event flush policy","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/ccr-heartbeat-can-adopt-a-server-pushed-event-flush-policy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### CCR heartbeat can adopt a server-pushed event flush policy\n\nCCR client can now adopt an event-flush policy pushed by the server in heartbeat responses\n\n**Unclear.** The finding does not say what CCR is or what effect changing the flush policy has in practice.\n\n**What**\n\nWhen the CCR client receives a response to its heartbeat, it now checks for an `event_flush_policy` field in the response data and, if present, calls a new `takeUpFlushPolicy` method to adopt it. This happens alongside the existing handling for refreshed authentication in heartbeat responses.\n\n**Why**\n\nThis lets the server adjust how the client flushes events at runtime by pushing a policy through the regular heartbeat, rather than that behavior being fixed on the client side.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}