{"version":"2.1.223","anchor":"background-job-state-and-roster-writes-can-route-through-the","canonical_anchor":"background-job-state-and-roster-writes-can-route-through-the","heading":"Background job state and roster writes can route through the v5 storage backend","tier":"soon","area":"Background Jobs","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/background-job-state-and-roster-writes-can-route-through-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Background job state and roster writes can route through the v5 storage backend\n\nBackground job files can be stored somewhere other than disk, but nothing switches that on yet.\n\n**What**\n\nJob `state.json`, the `order`\/`stateOrder`\/`group` sidecars and the roster orphan-adoption write each gained a branch that goes through a storage backend object instead of the filesystem, using versioned keys, `ifAbsent` preconditions and size caps. Filesystem behaviour is unchanged when no backend is supplied, and what turns the backend on could not be determined from source.\n\n**Details**\n\n- covers job state reads and writes, the three sidecar files, and the orphan-adoption seed write\n- failures on the backend path emit new warn-level diagnostics rather than throwing\n- when no backend object is handed in, the original filesystem path runs untouched\n\n**Evidence**\n\n`[jobs] v5 state write failed`\n\n- Area: Background Jobs\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}