Skip to Content
🇬🇧Task Scheduler

Task Scheduler — Automatic Tasks

Scheduler allows you to automatically run tasks on your game server — restarts, backups, commands, and other recurring actions.


Overview

FeatureDetails
Task typesCommand, Power, Backup
SchedulingCron expression
ConditionsOnly when running, chaining
Task limitPer package

Task Types

TypeDescription
CommandExecute console command
PowerStart, Stop, Restart, Kill
BackupCreate server backup

Creating a Scheduled Task

Step 1 — Open Scheduler

  1. Log in at coresynth.io 
  2. Go to Dashboard > Services
  3. Select your game server
  4. In sidebar, click Scheduler or Schedules

Step 2 — New Task

  1. Click New Task or Create Schedule
  2. Fill in settings:
    • Name — task identifier (e.g., “Daily restart”)
    • Task type — Command, Power, Backup
    • Command/Action — specific to type
  3. Set timing

Timing Setup

Cron Expression

Scheduler uses cron expression for precise timing:

FieldValueDescription
Minute0-59Minute in hour
Hour0-23Hour in day
Day of month1-31Day in month
Month1-12Month in year
Day of week0-6Sunday=0 to Saturday=6

Preset Options

PresetCronDescription
Every minute* * * * *Every minute
Every 5 minutes*/5 * * * *Every 5 minutes
Every hour0 * * * *Every hour
Every day0 0 * * *At midnight
Every week0 0 * * 0Sunday midnight
Every month0 0 1 * *First day of month

Examples

TaskCronDescription
Daily restart at 4:000 4 * * *Every day at 4:00 AM
Backup every 2 hours0 */2 * * *At 0:00, 2:00, 4:00…
Sunday restart0 4 * * 0Sunday at 4:00
Daily save30 */3 * * *Every 3 hours at :30

Task Conditions

Only When Running

When enabled:

  • Task runs only when server is running
  • If server is offline, task is skipped
  • Good for commands like save-all, say

Tip: For restarts and backups, keep this option disabled.

Task Chaining

You can chain tasks — run multiple tasks in sequence:

  1. Create first task
  2. In task settings, add “Continue to…”
  3. Select following task
  4. Tasks run in order

Common Scenarios

Daily Restart

Ensures server restarts daily to free memory:

FieldValue
NameDaily restart
TypePower
ActionRestart
Cron0 4 * * *
Only when runningNo

Automatic Backup

Creates backup every 6 hours:

FieldValue
NameAuto backup
TypeBackup
ActionCreate backup
Cron0 */6 * * *
Only when runningNo

Restart Announcement

Sends message to players 5 minutes before restart:

Task 1 — Announcement:

FieldValue
NameRestart warning
TypeCommand
Commandsay Server restarting in 5 minutes!
Cron55 3 * * *
Only when runningYes

Task 2 — Restart:

FieldValue
NameRestart
TypePower
ActionRestart
Cron0 4 * * *
Only when runningNo

Daily World Save

Saves world every 30 minutes:

FieldValue
NameAuto save
TypeCommand
Commandsave-all
Cron*/30 * * * *
Only when runningYes

Task Management

Viewing Tasks

In task list you see:

ColumnDescription
NameTask identifier
TypeCommand / Power / Backup
TimingCron expression
Next runDate and time
StatusActive / Inactive
ActionEdit / Delete

Editing Task

  1. Find task in list
  2. Click Edit
  3. Change settings
  4. Click Save

Deleting Task

  1. Find task in list
  2. Click Delete
  3. Confirm deletion

Manual Run

To run task immediately:

  1. Find task in list
  2. Click Run now
  3. Task executes immediately

Note: Manual run ignores “Only when running” condition.


Troubleshooting

Task Didn’t Run

Causes:

  • Server was offline (with “Only when running”)
  • Wrong cron expression
  • Task is inactive

Solution:

  1. Check server logs
  2. Verify cron expression
  3. Check that task is active

Wrong Timing

Cause: Incorrect cron expression.

Solution:

  1. Use preset options
  2. Test cron expression online (crontab.guru)
  3. Check server timezone

Backup Failed

Causes:

  • Insufficient disk space
  • Server running longer than timeout

Solution:

  1. Check disk space
  2. Reduce number of backups
  3. Delete old backups

Server Won’t Start After Restart

Cause: Startup error.

Solution:

  1. Check console logs
  2. Start server manually
  3. Verify configuration

Security Recommendations

  • Restart during off-hours — set restart at 3–5 AM
  • Backup regularly — but not too often (every 6–12 hours)
  • Test tasks — try manually before automating
  • Monitor logs — regularly check if tasks are running

Time Zones

Server uses UTC timezone.

When scheduling:

Central European TimeUTCExample
4:00 AM (winter)3:000 3 * * *
4:00 AM (summer)2:000 2 * * *

Tip: For simplicity, schedule when server is typically empty.


Next Steps


Need help? Open a support ticket  or ask Alex.

Last updated on