{"version":"2.1.248","anchor":"killed-background-tasks-leave-a-record-behind","canonical_anchor":"killed-background-tasks-leave-a-record-behind","heading":"Killed background tasks leave a record behind","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/killed-background-tasks-leave-a-record-behind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Killed background tasks leave a record behind\n\nKilling a background task keeps a record and its output file instead of losing both.\n\n**What**\n\nKilling a background bash task now records a snapshot of it against the owning agent before cleanup, with outcome \"killed\", no exit code, and the output file path kept, so the output is still reachable afterwards.\n\n**Details**\n\n- Skipped for tasks of kind \"monitor\".\n- Also depends on a runtime check whose condition is not visible from the built code.\n\n**Evidence**\n\n`rememberBashTaskSnapshot`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}