Skip to main content

Pause a Rust automation and know when it will come back

If a normal restart clashes with a tournament, give the exception a start and end. Keep the usual schedule available to restore. The next helper should be able to tell at a glance which run was skipped and who will put it back.

Put the exception beside the schedule

Write down the usual time and next run before changing anything. If your tool can skip one occurrence, check that the following occurrence remains scheduled. If it can only switch the whole job off, name the helper who will switch it back on and give them a reminder at a specific time.

An example is ‘Skip Saturday’s 19:00 UTC restart for the race. Mo will re-enable the job after the race and confirm next Saturday is still at 19:00 UTC.’ Add the actual dates so another helper can check your work.

Check warnings and missed runs before resuming

Find out whether the player warning is part of the restart or runs separately. If it has its own schedule, skip the warning for the same occurrence. Before turning either back on, check whether the scheduler can catch up on a missed action. If that would send an old notice or trigger a restart immediately, set the next run explicitly before you leave it unattended.

Check the newly displayed date and time against the original schedule. Tell the helper who owns the next window that the normal schedule is back.

Sources

Analytics settings

Analytics are off.

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