Reopening a stuck job in the fleet view now offers to force-restart it.
What's wrong with this entry?
Opening a job in the fleet view a second time now offers to restart it, forcing through a session that has stopped responding and replying on resume if the job was still active. If the old process is still alive after the attempt, the offer is re-armed and the error is shown with a prompt to press Enter and try again.
- The respawn is asked to force through an unresponsive session and, for active jobs, to send a reply once the session resumes.
- When the stop is not confirmed, the failure is recorded as
restart_stop_unconfirmedagainst the fleet view open event.
press Enter to try the restart again
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