Skip to main content

Which scheduled Rust jobs should wait until the wipe is over?

Look at the jobs that can run while you reset and verify the world. Pause or move any job that could interrupt that work. Record each change so the normal backup and update routine returns afterward.

Look outside the wipe screen

Read the next runs in the host panel, your management tool and any schedule on the host. Compare times in one zone. On a Linux host that uses systemd timers, systemctl list-timers shows next runs for timers currently loaded. For jobs you know are elsewhere, check those schedulers too.

Suppose the wipe starts at 19:00 UTC. A 19:05 UTC update that can restart the game belongs after verification unless it is part of your wipe. A 19:10 UTC backup can wait if it would copy a partly changed world. Keep the scheduled notice if it matches the current time and can still go out.

Look outside the wipe screen
Job to move or pauseWrite down
Ordinary backupIts controller, original next run and the next known-good backup to take
Unrelated restart or updateIts original schedule and when you want it to resume
Wipe noticesThe exact time and reset you told players to expect

Read the next runs after you reopen

Before re-enabling a job, check whether that scheduler runs missed work immediately. If it does, arrange an intentional next run that will not interrupt the newly opened world. Check that the deleted or completed one-off wipe cannot run a second time.

Your notes are complete when the ordinary backup and update schedules show the intended next times and the first backup after the wipe captures the playable world. If another person covers the next shift, give them the next-run list.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details