{"version":"2.1.248","anchor":"finished-background-tasks-would-carry-their-output-tail","canonical_anchor":"finished-background-tasks-would-carry-their-output-tail","heading":"Finished background tasks would carry their output tail","tier":"soon","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/finished-background-tasks-would-carry-their-output-tail","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Finished background tasks would carry their output tail\n\nCompletion notices would carry a finished task's output tail, on a disabled path.\n\n**What**\n\nOn the delivery path that is compiled off in this build, a finished background task's output tail is read before the completion notice goes out, so the notice would arrive with the tail attached.\n\n**Details**\n\n- If the read fails, the task is delivered without the tail and a warning \"output tail unreadable, delivering without it\" is logged.\n- Sits behind the same compiled-off guard as the GetTask surface, so nothing reaches users here.\n\n**Evidence**\n\n`output tail unreadable, delivering without it`\n\n- Area: Background Tasks\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}