Schedules

Scheduled Actions let you automate tasks and maintenance without doing them by hand. They save time by running commands, restarts, or other actions at set intervals.

Creating a new Scheduled Action

Go to the Schedules tab and you will find the Create Schedule button on the top right. After clicking, you will see a menu where you can configure:

• Schedule name: A human-readable identifier for this schedule
• Schedule Frequency: Choose from presets like "Every minute(s)", "Every hour(s)", "Every day(s)", etc.
• Interval: Set the number for your chosen frequency (e.g., every 5 minutes, every 2 hours)
• Only When Server Is Online: Only execute this schedule when the application is in a running state

The interface shows a preview of when your schedule will run, such as "Runs every 5 minute(s)".

The same menu is used when editing an existing schedule.

Managing Schedules

From the main schedules page, you can Pause or Resume schedules directly without having to delete and recreate them. This is useful when you need to temporarily disable a schedule.

Adding new tasks

After creating a schedule, go to the schedule management using the Manage Schedule button, and in the top right you'll find the New Task button for adding tasks to the schedule.

Clicking it opens a menu where you can select the task action, set its execution offset relative to the previous task in the chain, and configure additional parameters based on the chosen action.

Available task actions include:

• Send application console command: Execute a command in your application's console (for games and applications that accept console commands)
• Send environment console command: Execute a command in the Linux environment. This is useful for applications like websites that need to run scheduled tasks similar to cron jobs (e.g., php artisan schedule:run for Laravel)
• Send power action: Start, stop, restart, or kill your application
• Create backup: Create a backup of your server, counting toward your backup limit. See Backups for details
• Wait: Pause the task chain for a set duration before running the next task

You can reorder tasks in the chain by moving a row up or down, which changes the order in which they run.

Example schedule

For example, let's create a scheduled task to restart the application every 12 hours with a warning message.

Creating a new schedule

Click the Create Schedule button, name it "Server auto-restart", set the frequency to "Every hour(s)" with an interval of 12, which means it will run every 12 hours. We'll also enable the "Only When Server Is Online" flag so that this schedule doesn't run if the application is offline.

Adding tasks to the schedule

Now, let's add the first task to our chain. Click the New Task button, select the Application Command action, and in the Payload field enter say Scheduled server auto-restart in 15 seconds!.

Next, let's add the second task to the chain. Click the New Task button again. This time, select the Send Power Action, set the Time Offset field to 15 so that the application restarts 15 seconds after the message is sent, and choose Restart in the Payload field.

Great! We have created a task to automatically restart the application every 12 hours. To test it, you can click the Run Now button on the schedule management page.

How does it work

Every 12 hours, the message "Scheduled server auto-restart in 15 seconds!" is sent, and 15 seconds later the application receives the restart task. You can experiment with execution time, number of tasks in the chain, and even the types of tasks.