{"version":"2.1.275","anchor":"some-aborttracking-object-hn-removed-from-remote-session","canonical_anchor":"some-aborttracking-object-hn-removed-from-remote-session","heading":"Some abort\/tracking object (HN) removed from remote-session hook wiring","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/some-aborttracking-object-hn-removed-from-remote-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Some abort\/tracking object (HN) removed from remote-session hook wiring\n\nAn abort-tracking object is no longer created in remote session hook setup\n\n**Unclear.** What the removed object tracked and what effect its removal has isn't stated in the evidence.\n\n**What**\n\nIn the code that wires up remote\/thin-client sessions, an object that used to be conditionally created (when a certain internal flag was true) is now never instantiated at all, in both of the relevant session-hook code paths.\n\n**Why**\n\nWhatever tracking or abort-handling this object provided is no longer active in these remote session paths; the practical effect for users isn't specified.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}