Lagless

Schedules

Automate restarts, backups, alerts, and more with scheduled tasks

Updated

Schedules

Schedules automate routine tasks on your server — restarts, backups, alerts, and more. You can build one from scratch, or start from a ready-made template in one click.


Method 1: Use a Template

Templates are the fastest way to get started. They cover the most common automations and configure everything for you.

  1. Log in to the Game Panel

  2. Click Manage server

  3. In the left sidebar, scroll to the Utility section

  4. Click Schedules

  5. Open the schedule templates picker

  6. Filter by category — All, Maintenance, Backups, Performance, Minecraft, or Alerts

  7. Click the template you want

  8. Review the pre-filled settings and adjust if needed

  9. Click Activate

Schedule Templates

Some templates create more than one task. For example, Sleep at night creates two tasks, one to stop the server and one to start it again.


Method 2: Build One Manually

Use this method when no template fits, or when you want full control.

Step 1: Create the Schedule

  1. Log in to the Game Panel
  2. Click Manage server
  3. In the left sidebar, scroll to the Utility section
  4. Click Schedules
  5. Click Create schedule

Create Schedule

  1. Under Name, enter a human-readable identifier for the schedule

  2. Under When should it run?, leave the Trigger on On a schedule (time) — this runs the schedule at the times defined by the cron expression

  3. Pick how often the schedule should run using one of the two tabs:

    Quick (default) — pick from a list of common intervals:


    • Every 5 minutes
    • Every 15 minutes
    • Every 30 minutes
    • Every hour
    • Every 6 hours
    • Every 12 hours
    • Once a day
    • Every Monday
    • Once a week
    • Once a month

    Advanced, fine-tune the exact timing with a custom cron expression using the Minute, Hour, Day of month, Month, and Day of week fields. Enable Show Cheatsheet for a quick reference if needed.

  4. Review the Summary panel on the right, it confirms in plain language when the schedule will run

  5. Optionally add conditions under Only if..., every condition must be true for the schedule to run. Leave empty to always run.

  6. Under Options, toggle Schedule Enabled on (default) to activate the schedule immediately after saving

  7. Click Create schedule

Create New Schedule

Step 2: Add a Task

  1. Click Manage schedule on the schedule you just created
  2. Click New Task
  3. Choose an action:
ActionWhat it does
Send commandSends a console command to the server.
Send power actionStart, restart, stop, or forcibly terminate the server.
Create backupCreates a backup. Optionally exclude files/folders — defaults to your .pteroignore rules.
Send webhookSends an HTTP request to a URL (Discord, Slack, or any endpoint). Use the Discord, Slack, or Generic templates for a quick start.
  1. Set a Time offset (in seconds) if this task should wait after the previous one runs. Ignored for the first task, max 900 seconds.
  2. Optionally enable Continue on Failure so later tasks still run even if this one fails.
  3. Click Create Task

Edit Schedule

You can add as many tasks as you want to a single schedule. Use a time offset on each task to control the order they fire in.


Example: Daily Restart with Discord Warning

Goal: Restart the server every day at 12:00, with a Discord heads-up 10 seconds before.

  1. Create a schedule using Advanced mode:

    • Minute: 0
    • Hour: 12
    • Day of month: *
    • Month: *
    • Day of week: *

    Daily Restart example

  2. Add a task for the Discord notification:

    • Action: Send webhook
    • Webhook URL: Your Discord webhook URL
    • Payload: Use the Discord template button, then customize
    • Time offset: 0 seconds (fires immediately at 12:00)

    Discord webhook example

  3. Add a second task for the restart:

    • Action: Send power action
    • Payload: Restart the server

    Daily Restart example

The webhook fires first (10-second offset), then the server restarts at 12:00.

Daily Restart example


Task Action Reference

ActionCommon use
Send commandSchedule events, broadcast /say messages before a restart
Send power actionRestart servers on a schedule
Create backupNightly backups while nobody is online
Send webhookNotify Discord/Slack (or any endpoint) when a schedule runs