{"version":"2.1.248","anchor":"stale-auto-resume-jobs-are-marked-stopped-rather-than-failed","canonical_anchor":"stale-auto-resume-jobs-are-marked-stopped-rather-than-failed","heading":"Stale auto-resume jobs are marked stopped rather than failed","tier":"notice","area":"Background Jobs","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/stale-auto-resume-jobs-are-marked-stopped-rather-than-failed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Stale auto-resume jobs are marked stopped rather than failed\n\nAbandoned auto-resume jobs are recorded as stopped, keeping them out of your failure list.\n\n**What**\n\nA job set to auto-resume that reports a failure while it is not alive and has not been updated for longer than a threshold is now recorded as stopped, with a canned explanation, instead of failed. This keeps abandoned jobs out of your failure list.\n\n**Details**\n\n- The state write is now awaited, and the routine reports \"none\" when it takes no action.\n\n**Evidence**\n\n`o?.resumable === \"auto-resume\"`\n\n- Area: Background Jobs\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}