An Automation Didn't Run
Use this guide when Auto-start, Auto-shutdown, or Repeating Broadcast did not have the expected result. A saved rule is not proof that its action completed.
Check the saved rule
Open the correct server's Automation section and inspect the rule before editing:
- Is the intended day selected under Active days?
- Is the intended action enabled, with a time entered?
- Does Timezone match the clock used to choose the time? The schedule follows that timezone, not necessarily your current device's timezone.
- Were the changes saved? Reopen the section and check the values rather than relying on an old form.
Auto-start and Auto-shutdown are independent. To turn an action off, disable it; when enabling an action, enter its time. An incomplete form or validation message does not change the saved schedule. If the section is read-only, ask the owner to check your automation permission.
Compare the state at the scheduled time
Review Activity Log around the occurrence, including the date and timezone:
- Auto-start does not restart a server that is already running.
- Auto-shutdown has nothing to stop if the server is already stopped. It can stop a running server even with connected players.
- Auto-start follows normal billing: unused banked time can resume, but otherwise the owner's balance must cover a full hour. Configuration upgrades may require extra credit.
- A current balance does not prove that sufficient credit was available when the action was due.
A failed or skipped occurrence is not retried later. Topping up does not rerun it. After resolving the cause, use Start manually if you want to play now, or wait for the next selected occurrence. Let any in-progress lifecycle operation finish before submitting another action.
If Repeating Broadcast sent no message
The section appears only for games with supported broadcasting. Check that the feature is enabled, at least one message is saved, and the chosen interval is what you intended. Reopen the section to confirm the saved values.
The server must be Running to send a message. Allow a full configured interval while it is running; messages are not promised at the exact second a timer reaches zero. Ask a connected player to check the game's message display.
Messages pause while stopped; missed messages are not delivered later as a backlog. With several messages, one is sent per interval in rotation, not all at once.
Correct and verify once
Change only the incorrect day, action, time, or timezone, then select Save schedule and confirm Schedule saved. For a broadcast change, select Save broadcast and confirm Broadcast saved. Reopen the section to verify the saved rule.
Check the next intended occurrence and resulting server state, or the next broadcast interval. Do not create repeated short-lived schedules just to force a result: scheduled starts can spend credit and shutdowns disconnect players.
See Auto-start and Auto-shutdown and Repeating Broadcast.
When to contact support
Contact support if a correctly saved rule still has no expected effect, its save repeatedly fails, or the server becomes stuck during the scheduled action.
Include the server name, selected days, action, local scheduled time, timezone, observed status, and relevant Activity Log times. For broadcasts, include the interval and whether players were connected. Remove private message content and unrelated account details from screenshots.