You'll notice
Useful2 Signal2
Restarting a background job waits for any spawn already running instead of starting a second.
What's wrong with this entry?
Anonymous. No account, no email.
What
Respawning 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.
Evidence
in_flight_spawn_failed
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.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task