Skip to main content

Why did a scheduled Rust restart not happen?

Check the scheduler’s last run before triggering the restart again. The schedule may not have fired, its command may have failed, or the game may already have restarted.

Follow the record in order

Check whether the task was enabled and whether the host was awake at its due time. For a systemd calendar timer, check whether it is set to catch up after downtime. On Windows, open the task history or inspect its last run details. If the schedule ran, look for the game’s stop and new startup in its own log.

Confirm exactly one restart

If you find a path error, fix it and check the next due time with the right time zone. If the restart may still be pending, check that before starting one manually. At the next announced window, confirm that the game process starts once and players can reconnect.

Sources

Analytics settings

Analytics are off.

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