
Should a missed Rust job run when the host comes back?
Decide what a late run should mean before the first outage. If an early-morning restart would land in a busy afternoon, you may want to skip it. If a housekeeping job can still help later in the day, running it once when the host returns may suit you.
Find the setting that handles missed time
Read the scheduler’s policy for an offline host and for an offline game. Windows Task Scheduler has a setting for starting a timed task after its scheduled time has passed. A systemd calendar timer can catch up with Persistent= enabled. A game panel may have its own rule. Check the scheduler that actually owns this job.
Write the decision beside the job. ‘Skip the early restart if the host missed its window. The next regular run stays on the calendar.’ If the tool can only catch up, choose a different route for a job that would disrupt players later in the day.
Rehearse a missed run without restarting your live world
Use a spare host or scheduler and a harmless task whose output you can recognise. If the real job must handle a missed run because its host was powered off, reproduce that on the spare host.
- Schedule a test job that leaves a timestamp you can check later.
- Keep the spare host off while the scheduled time passes, then turn it back on.
- Compare when the job ran, if at all, with the intended catch-up rule. Check that the next regular run remains in place.