Schedule restarts and automations

Restart on a schedule with in-game warnings, or run "when this happens, do that" rules. Operator: 5 rules. Network: unlimited.

Using the dashboardUpdated 2 min read

Open Build, then Automations. You need to be able to manage servers; saved commands also need permission to run commands.

Scheduled restarts

Pick daily, weekly or quietest, a timezone and a time. Quietest chooses the hour with the fewest players from 28 days of data. Choose the warnings to send, from 30 down to 1 minute before (default 15, 10, 5 and 1) and a final message 10 seconds before. The restart is a saved restart command or an agent that supports restarts.

Triggers

A trigger has a condition and up to 3 actions. Conditions: server offline for N minutes, players above or below a value, a metric (such as TPS) over a threshold, a lag-spike burst, or an alert firing. Actions: send an in-game message, run a saved command, restart (not with server offline), or notify a channel. Triggers have a cooldown (default 15 minutes), a cap of runs per day (default 6) and start in dry run, which only records what would have happened.

Safety

  • The server must have remote actions on, in the agent config and in the dashboard.
  • Everything is audited. Rules run as the member who last saved them; if that member loses permission or leaves, the rule is switched off.
  • A warning that cannot be delivered cancels the restart. A step more than 2 minutes late is skipped.
  • There is an organisation-wide kill switch: pausing automations cancels open runs and nothing runs until you resume.
  • Not every agent can restart a server yet: a run on an unsupported agent is skipped with the reason unsupported. Check the agent's capabilities on its game page.

Related

Using the dashboardBuildCustom events and funnels, saved dashboards and automations: charts and rules for what your own plugins send.Using the dashboardPerformanceServer health for your game (TPS, MSPT or FPS), lag spikes named by plugin or resource, network quality and the quietest window to restart.Using the dashboardModerationThe Logs explorer for payments, trades and punishments, abuse flags, punishments, staff activity and bans across servers.
Still stuck? Email [email protected] with the server name and what you see. For a rejected claim code or no data, include the output of the agent’s status command.