You'll notice
Useful2 Signal2
Abandoned auto-resume jobs are recorded as stopped, keeping them out of your failure list.
What's wrong with this entry?
Anonymous. No account, no email.
What
A 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.
Details
- The state write is now awaited, and the routine reports "none" when it takes no action.
Evidence
o?.resumable === "auto-resume"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Background job state and roster writes can route through the v5 storage backend
Both mention background
-
v2.1.223
Telemetry for transient background-job state read failures
Both mention background
-
v2.1.223
Roster orphan adoption reports itself
Both mention background