{"version":"2.1.248","anchor":"background-jobs-that-died-while-the-service-was-off-get-mark","canonical_anchor":"background-jobs-that-died-while-the-service-was-off-get-mark","heading":"Background jobs that died while the service was off get marked and need a confirm to reopen","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/background-jobs-that-died-while-the-service-was-off-get-mark","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Background jobs that died while the service was off get marked and need a confirm to reopen\n\nBackground jobs that died while the service was off are marked stopped and need a confirm to reopen.\n\n**What**\n\nWhen a background job is found failed and unresumable and its record is older than 48 hours (172800000 ms), Claude Code now marks it as stopped with the note that it ended while the background service was off. Reopening it from fleet view takes a second press to confirm. No flag guards any of this.\n\n**Details**\n\n- The mark is cleared once the session is successfully respawned.\n- Fleet view records `tengu_fleetview_dead_epoch_offer` when it shows the confirmation.\n- The session roster gained an epoch accessor alongside status and last-heard-at.\n\n**Evidence**\n\n`ended while the background service was off`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}