{"version":"2.1.248","anchor":"headless-output-failures-report-a-transport-write-failure-in","canonical_anchor":"headless-output-failures-report-a-transport-write-failure-in","heading":"Headless output failures report a transport write failure instead of raw error text","tier":"notice","area":"Headless Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/headless-output-failures-report-a-transport-write-failure-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Headless output failures report a transport write failure instead of raw error text\n\nHeadless output failures say \"transport write failure\" and put the real reason in the log.\n\n**What**\n\nWhen the output stream dies in headless mode, the \"session has ended\" message now says \"transport write failure\" for redacted or remote sessions rather than printing the underlying error. The full reason is written to the error log instead.\n\n**Evidence**\n\n`Could not write a message to the output stream (`\n\n- Area: Headless Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}