Overview
Schedules allow you to automate repetitive tasks on your game server using cron expressions. Create scheduled backups, automated restarts, timed announcements, and complex task chains that execute in sequence.Accessing Schedules
Navigate to your server’s schedule management:Creating a Schedule
Configure Schedule
Fill in the schedule details:
- Schedule Name: Descriptive name (e.g., “Daily Restart”)
- Cron Expression: When to run (see Cron Timing below)
- Enabled: Whether the schedule is active
Request Body Example
Request Body Example
Cron Timing
Schedules use standard cron syntax with 5 fields:Cron Fields
- Minute
- Hour
- Day of Month
- Month
- Day of Week
0-59: Minute of the hourExamples:
0= Top of the hour30= Half past the hour*/5= Every 5 minutes*= Every minute
Quick Presets
Use the preset buttons for common schedules:Every Minute
Every 5 Minutes
Every Hour
Daily at Midnight
Weekly on Sunday
Example Cron Expressions
Common Schedules
Common Schedules
0 4 * * *= Daily at 4:00 AM0 */6 * * *= Every 6 hours30 2 * * 0= Every Sunday at 2:30 AM0 0 1 * *= First day of every month at midnight*/30 * * * *= Every 30 minutes0 6 * * 1-5= Weekdays at 6:00 AM
Schedule Tasks
Each schedule can have multiple tasks that execute in sequence. Tasks run in order based on their sequence ID with optional time offsets.Task Types
Schedules support three types of tasks:- Command
- Power
- Backup
Execute a console command:
- Action:
command - Payload: The command to run (e.g.,
say Server restarting in 5 minutes) - Example use: Announcements, world saves, custom commands
Adding Tasks
Configure Task
Fill in the task details:
- Payload: Command text, power action, or backup name
- Time Offset: Seconds to wait before executing (0-3600)
- Continue on Failure: Whether to continue if this task fails
Request Body Examples
Request Body Examples
Command Task
Power Task
Backup Task
Task Execution Order
Tasks execute sequentially in order of their Sequence ID:- Sequence ID #1 executes at schedule trigger time
- Wait for Task #1’s time offset
- Execute Task #1
- If
continue_on_failureis false and task fails, stop here - Wait for Task #2’s time offset
- Execute Task #2
- Continue until all tasks complete
Time Offsets
Time offsets delay task execution:- 0 seconds: Execute immediately
- 60 seconds: Wait 1 minute before executing
- 300 seconds: Wait 5 minutes
- 3600 seconds: Wait 1 hour (maximum)
Example Schedules
Daily Restart with Warnings
Hourly Backups
Weekly Maintenance
Managing Schedules
Edit Schedule
- Click the Edit button on a schedule
- Modify the name, cron expression, or enabled status
- Click Save
POST /api/client/servers/{server}/schedules/{schedule}
Force Run
Manually trigger a schedule:- Click the Force Run button
- All tasks execute immediately regardless of cron timing
- Useful for testing schedules
POST /api/client/servers/{server}/schedules/{schedule}/run
Delete Schedule
- Click the Delete button
- Confirm deletion in the modal
- Schedule and all tasks are removed
DELETE /api/client/servers/{server}/schedules/{schedule}
Schedule Status
Schedules display their current status:Enabled
Schedule is active and will run at the next scheduled time.
Paused
Schedule is disabled and will not run until re-enabled.
Schedule Information
Each schedule shows:- Cron Expression: The timing pattern
- Task Count: Number of configured tasks
- Next Run: When the schedule will next execute
- Last Run: When the schedule last executed
Task Management
Editing Tasks
Tasks cannot be edited directly. To modify a task:- Delete the existing task
- Create a new task with updated settings
Deleting Tasks
- Open Manage Tasks for the schedule
- Click the trash icon next to a task
- Confirm deletion
- Task is removed from the sequence
DELETE /api/client/servers/{server}/schedules/{schedule}/tasks/{task}
Reordering Tasks
Tasks execute in sequence order (Sequence ID). To reorder:- Delete tasks you want to reorder
- Re-create them in the desired order
- Tasks are automatically assigned sequential IDs
Permissions
Schedule management requires:- View schedules:
server.schedule.read - Create schedules:
server.schedule.create - Edit schedules:
server.schedule.update - Delete schedules:
server.schedule.delete - Manage tasks:
server.schedule.update
Best Practices
Test First
Use Force Run to test schedules before relying on them for important tasks.
Add Warnings
For restart schedules, announce ahead of time so players can prepare.
Use Continue on Failure
Enable for power actions so later tasks still execute if one fails.
Stagger Backups
Don’t schedule all servers’ backups at the same time to avoid performance issues.
Troubleshooting
Schedule not running
Schedule not running
- Check that the schedule is Enabled (not paused)
- Verify the cron expression is correct
- Ensure the schedule has at least one task
- Check server logs for execution errors
Tasks executing in wrong order
Tasks executing in wrong order
- Tasks run by sequence ID, which is assigned in creation order
- Delete and recreate tasks in the correct order if needed
Command task not working
Command task not working
- Verify the command syntax is correct for your game
- Check server console for command output/errors
- Ensure the server is running when the command executes
API Reference
List Schedules
Response Example
Response Example
Next Steps
Backups
Learn about manual and automated server backups
Server Console
Monitor schedule execution in the real-time console