Schedules
Automate server tasks with the built-in scheduler. Run commands, create backups, and manage power actions on a schedule.
Accessing Schedules
- Select your server from the dashboard
- Click Schedules in the left sidebar
Creating a Schedule
Step 1: Create New Schedule
- Click Create Schedule
- Enter a name (e.g., “Daily Restart”)
- Configure the timing
Step 2: Set the Timing
Use cron-style timing:
| Field | Values | Description |
|---|
| Minute | 0-59 | Minute of the hour |
| Hour | 0-23 | Hour of the day (24h format) |
| Day of Month | 1-31 | Day of the month |
| Month | 1-12 | Month of the year |
| Day of Week | 0-6 | Day (0 = Sunday) |
Common Schedules
| Schedule | Cron Expression | Timing |
|---|
| Daily at 4 AM | 0 4 * * * | Every day at 4:00 AM |
| Every 6 hours | 0 */6 * * * | 12AM, 6AM, 12PM, 6PM |
| Weekly Monday | 0 3 * * 1 | Every Monday at 3:00 AM |
| Every hour | 0 * * * * | Start of every hour |
Step 3: Add Tasks
Each schedule can have multiple tasks that run in sequence.
Task Types
| Type | Description |
|---|
| Send Command | Execute a console command |
| Send Power Action | Start, stop, restart, or kill |
| Create Backup | Create a server backup |
Step 4: Save and Enable
- Review your schedule configuration
- Click Save
- Ensure the schedule is enabled
Example Schedules
Daily Restart with Warning
Schedule: Daily at 4 AM
| Order | Task | Payload | Delay |
|---|
| 1 | Command | say Server restarting in 5 minutes! | 0s |
| 2 | Command | say Server restarting in 1 minute! | 240s |
| 3 | Power | Restart | 60s |
Hourly Backup
Schedule: Every hour
| Order | Task | Payload |
|---|
| 1 | Backup | (creates backup) |
Weekly Maintenance
Schedule: Every Sunday at 3 AM
| Order | Task | Payload | Delay |
|---|
| 1 | Command | say Weekly maintenance starting... | 0s |
| 2 | Backup | (creates backup) | 60s |
| 3 | Power | Restart | 120s |
Managing Schedules
Edit a Schedule
Click on the schedule to modify timing or tasks.
Enable/Disable
Toggle the schedule on or off without deleting it.
Delete
Remove the schedule entirely.
Run Now
Execute the schedule immediately (useful for testing).
Task Delays
Add delays between tasks to space out actions:
Task 1: Send warning → 0 seconds
Task 2: Send final warning → 240 seconds (4 min later)
Task 3: Restart → 60 seconds (1 min later)
Best Practices
- Add warnings before restarts so players can save
- Schedule restarts during low-activity hours
- Regular backups - at least daily
- Test schedules using “Run Now” before relying on them
- Stagger tasks to avoid conflicts
Schedule restarts during your server’s quietest hours to minimize player disruption.
Troubleshooting
Schedule Not Running
- Check if the schedule is enabled
- Verify the cron timing is correct
- Ensure the server is online (for commands)
Tasks Not Executing
- Check task order and delays
- Review console for error messages
- Verify command syntax is correct
Next Steps