{"version":"2.1.265","anchor":"bug-fix-sessionsv2clientpostevents-read-the-wrong-variable","canonical_anchor":"bug-fix-sessionsv2clientpostevents-read-the-wrong-variable","heading":"Bug fix: SessionsV2Client.postEvents read the wrong variable for sequence_num","tier":"notice","area":"Session Management","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/bug-fix-sessionsv2clientpostevents-read-the-wrong-variable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Bug fix: SessionsV2Client.postEvents read the wrong variable for sequence_num\n\nFixed a bug where session event posting logged the wrong sequence number\n\n**What**\n\nThe internal function that posts session events (`SessionsV2Client.postEvents`) was reading the `sequence_num` value from the wrong variable \u2014 one that wasn't the actual result returned by the request. It now correctly reads `sequence_num` from the parsed result.\n\n**Why**\n\nThis fixes incorrect sequence numbers being recorded for session events, which could otherwise throw off anything that relies on events being tracked in the right order.\n\n- Area: Session Management\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}