{"version":"2.1.247","anchor":"the-ccr-v2-event-send-switch-now-defaults-on","canonical_anchor":"the-ccr-v2-event-send-switch-now-defaults-on","heading":"The CCR v2 event-send switch now defaults on","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/the-ccr-v2-event-send-switch-now-defaults-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### The CCR v2 event-send switch now defaults on\n\nThe newer cloud event-sending path is now the default when the server has no opinion.\n\n**What**\n\nThe setting `tengu_ccr_v2_send_events_cli`, which selects the newer path for sending cloud session events, now falls back to enabled when the server expresses no opinion. It previously fell back to disabled. The real value still comes from remote config.\n\n**Details**\n\n- Nothing else in the bundle references the local name of the check, so which send path this default now turns on cannot be pinned down from the build alone.\n- Related churn in the cloud sessions client in the same change threads a per-call timeout through event posts and control responses, consistent with the v2 path being prepared for real traffic.\n\n**Evidence**\n\n`tengu_ccr_v2_send_events_cli`\n\n- Flag `tengu_ccr_v2_send_events_cli`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.247; this account: on, anonymous baseline: on, compiled default: on)\n- Area: Cloud Sessions\n- Names: `tengu_ccr_v2_send_events_cli`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}