Runbooks can use triggers to start on schedule. If the OctopusDeploy service stops for any reason, a runbook that has missed its schedule will run as soon as OctopusDeploy become available. This is suboptimal where the missed trigger was powering off some VMs overnight and runs during your core hours, for example. This behavior should be configurable, much like the "Run task as soon as possible after a scheduled start is missed" setting in Windows scheduled tasks.