{"version":"2.1.248","anchor":"tasks-that-die-outright-are-distinguished-from-tasks-that-fi","canonical_anchor":"tasks-that-die-outright-are-distinguished-from-tasks-that-fi","heading":"Tasks that die outright are distinguished from tasks that finish","tier":"internal","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/tasks-that-die-outright-are-distinguished-from-tasks-that-fi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Tasks that die outright are distinguished from tasks that finish\n\nBackground tasks that die are now distinguished from ones that finish normally.\n\n**What**\n\nThe step that decides a background task has come to rest now reports three outcomes instead of two: a dead worker generation, a normal settle, or nothing to do.\n\n**Details**\n\n- Dead generations record a `deadEpochReapedAt` timestamp rather than the mid-work reap timestamp.\n- In that case the first terminal time is taken from the previous update time instead of the current one.\n\n**Evidence**\n\n`deadEpochReapedAt`\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}