{"version":"2.1.265","anchor":"likely-bug-fix-postkeptresponse-referenced-the-wrong-variab","canonical_anchor":"likely-bug-fix-postkeptresponse-referenced-the-wrong-variab","heading":"Likely bug fix: postKeptResponse referenced the wrong variable","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/likely-bug-fix-postkeptresponse-referenced-the-wrong-variab","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Likely bug fix: postKeptResponse referenced the wrong variable\n\nFixed a bug where a remote session's postKeptResponse used the wrong response data\n\n**What**\n\nIn the code that manages remote sessions, a method called `postKeptResponse` was sending a control response built from a variable belonging to an outer, unrelated scope instead of its own parameter. It now correctly uses its own parameter's data when sending the response.\n\n**Why**\n\nThis was a bug that could cause the wrong response data to be sent back for a kept response in a remote session; fixing it ensures the response actually sent matches the one that was meant to be kept.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}