{"version":"2.1.247","anchor":"cloud-event-sending-defaults-to-the-v2-api","canonical_anchor":"cloud-event-sending-defaults-to-the-v2-api","heading":"Cloud event sending defaults to the v2 API","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/cloud-event-sending-defaults-to-the-v2-api","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Cloud event sending defaults to the v2 API\n\nCloud session events now go to the v2 API by default; session reads and writes still do not.\n\n**What**\n\nThe built-in default for sending cloud session events flipped from off to on, so without a server value the CLI uses the v2 sessions API. The companion switch for v2 session create\/read\/update still defaults off, so only the event path moved. The live value still comes from remote config.\n\n**Evidence**\n\n`isCcrV2SendEventsEnabled`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}