Automations

Move recurring server work out of memory and into schedules whose action, timing, state and outcome remain visible.

Create a scheduled task

1. Select the server, then open Scheduler.
2. Choose a supported action.
3. Enter the action-specific settings.
4. Select the intended clock time, active days and timezone.
5. Review the next-run preview.
6. Save the task and confirm it appears as active.

Safe first execution

For a new automation type, begin with a controlled time while an owner can observe the server. Confirm the agent is connected, the task is claimed once, the expected operation occurs and the reported result appears in history.

Edit, pause or remove

Disable a task when it should not run but you want to keep its definition. Edit timing or payload when the routine changes. Remove it only when the definition is no longer useful. After any edit, review the recalculated next-run value.

Saved operations

Saved locations, kits and operation templates are useful for work that should be consistent but still triggered manually. Give templates unambiguous names, include only the intended parameters and retire obsolete versions so administrators do not choose the wrong one during a live event.

Operational checklist

• The agent and RCON path are healthy.
• The scheduled user or workspace still has the required entitlement.
• The task is active and its next run is correct.
• Player communication is configured where disruption is expected.
• A team member knows how to pause the task if conditions change.
• Recent outcomes are reviewed after the first execution and after edits.