{"version":"2.1.246","anchor":"restarting-a-background-job-no-longer-races-a-spawn-already-","canonical_anchor":"restarting-a-background-job-no-longer-races-a-spawn-already-","heading":"Restarting a background job no longer races a spawn already under way","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/restarting-a-background-job-no-longer-races-a-spawn-already-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Restarting a background job no longer races a spawn already under way\n\nRestarting a background job waits for any spawn already running instead of starting a second.\n\n**What**\n\nRespawning a background or fleet session now waits for any spawn already in flight for that job rather than starting a second one. If that spawn failed and left nothing running, the respawn stops with the failure reason `in_flight_spawn_failed` and queues the initial prompt instead of double-spawning.\n\n**Evidence**\n\n`in_flight_spawn_failed`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}