An Automation Didn't Run

Use these checks when Auto-start, Auto-shutdown, or Repeating Broadcast did not produce the result you expected.

Symptom: Auto-start or Auto-shutdown did not change the server

Open the server's Automation section and check:

1. The intended day is selected under Active days.
2. The correct action is enabled and has a time. An empty time turns that action off.
3. Timezone matches the location whose clock you used when choosing the time.
4. The page showed Schedule saved. after your last change.

An Auto-start occurrence does not restart a server that is already running. An Auto-shutdown occurrence does not change a server that is already stopped.

Check Credit Balance and server state

Auto-start needs enough credit in the owner's Credit Balance to start the server. If credit was too low at the scheduled time, top up and start the server manually; that missed occurrence is not retried later.

Wait for any current Starting or Stopping operation to finish. Then review the Activity Log for the server state around the scheduled time.

Symptom: Repeating Broadcast sent no message

Check all of the following:

• Repeating Broadcast is available for this game and is enabled.
• At least one message is present and the page showed Broadcast saved.
• The server was Running when the interval came due.
• The interval has elapsed since the server became available to send messages.

Messages pause while the server is stopped; missed messages are not sent later as a backlog. With multiple messages, one message is sent per interval in rotation.

Next action

Save the rule again after correcting any day, time, timezone, interval, or message. If the next scheduled occurrence still fails, keep the server name, selected timezone, scheduled local time, and the relevant Activity Log time ready when contacting Support.