{"version":"2.1.225","anchor":"background-job-state-keeps-respawn-flags-and-non-allowlisted","canonical_anchor":"background-job-state-keeps-respawn-flags-and-non-allowlisted","heading":"Background job state keeps respawn flags, and non-allowlisted tokens are stripped","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/background-job-state-keeps-respawn-flags-and-non-allowlisted","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Background job state keeps respawn flags, and non-allowlisted tokens are stripped\n\nBackground jobs now save the flags needed to relaunch them, dropping any unrecognised flags with a warning.\n\n**What**\n\nPersisted background job state now carries the flags needed to respawn a job, with unknown flag tokens filtered out before they are written.\n\n**Details**\n\n- the job-state writer persists `respawnFlags` alongside the fields it already rewrites\n- the schema defaults `respawnFlags` to an empty list and filters its contents against an allowlist\n- dropped tokens produce a warning naming them\n\n**Evidence**\n\n`[jobs] stripped non-allowlisted respawnFlags token(s) from persisted job state: `\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}