{"version":"2.1.265","anchor":"remote-headless-client-host-request-logger-bug-fix-correct","canonical_anchor":"remote-headless-client-host-request-logger-bug-fix-correct","heading":"Remote headless client host-request logger bug fix: correct outcome value now logged","tier":"notice","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/remote-headless-client-host-request-logger-bug-fix-correct","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Remote headless client host-request logger bug fix: correct outcome value now logged\n\nFixed a bug where the remote headless client's request logger recorded the wrong outcome value\n\n**What**\n\nAn internal logging helper used by the headless (non-interactive) cloud client was recording telemetry with an `outcome` value taken from an unrelated outer-scope variable instead of the actual outcome parameter passed into the function. It now correctly logs the outcome that was actually passed in.\n\n**Why**\n\nThis fixes inaccurate outcome data being recorded for host requests made by the remote headless client, which would have made related telemetry unreliable.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}