Rust Admin's scheduler sends server commands on a cron schedule, making recurring maintenance easier to organise.
Check automatic startup first
Your host or startup script must restart the Rust process after it exits. A command delivered to the running agent cannot launch an already stopped process. Perform the first restart while you can supervise it.
Create the task
- Select one server in Scheduler.
- Give the task a clear name and enter
restart. - Use a schedule such as
0 5 * * *for 05:00 daily in the scheduler process's timezone. Verify the next execution shown in the panel against your local time. - Schedule a separate player announcement before maintenance.
Test timing with a harmless chat announcement first. Avoid enabling a task for the current minute unless you are ready for immediate execution.
Verify the result
Check the last execution, task error, console and agent reconnection. Command delivery alone does not prove the game restarted successfully. Availability notifications help track the transition. A restart is not a wipe, and recurring restarts do not replace investigating the underlying cause of lag.
See the workflow in Rust Admin
The interface demonstration below uses sample data to illustrate the section. These are not measurements from your server.
Open the Rust Admin scheduler and test an announcement on one server first. Sign in with Steam · View plans
