{"version":"2.1.269","anchor":"remote-headless-session-attach-can-serve-a-device-link-direc","canonical_anchor":"remote-headless-session-attach-can-serve-a-device-link-direc","heading":"Remote headless session attach can serve a device link directly instead of waiting on session state","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/remote-headless-session-attach-can-serve-a-device-link-direc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Remote headless session attach can serve a device link directly instead of waiting on session state\n\nRemote headless session attach can now get a device link directly instead of waiting on polled session state\n\n**Unclear.** The finding does not specify what condition triggers the direct device-link path.\n\n**What**\n\nWhen a certain condition is met, attaching to a remote headless session now uses a new `linkForServing` helper to get a device ID directly, rather than always waiting for and deriving the connection from polled session state. A new failure telemetry action, `attach_serve_link`, was added to track when this path fails.\n\n**Why**\n\nThis can make attaching to a remote session faster in the cases where the direct path applies, by skipping the wait for polled state.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}