A schedule is a small automation that runs on your server without you being there: restart every night, back up before a big event, run a command when a player joins, restart if it ever crashes. Every schedule is the same two-part idea — a trigger that decides when, and an ordered list of tasks that decide what happens. Open Schedules from your server menu to build one.
| At a glance | |
|---|---|
| You need | Any Falix server |
| Plan | All plans — free runs the Command task while online; other tasks and offline running are premium |
| Time | Fifteen minutes |
Pick a trigger
When you create a schedule you choose one of six types:
| Trigger | When it runs |
|---|---|
| Interval | On a repeating gap — presets 5 / 15 / 30 minutes and 1 / 2 / 6 / 12 hours |
| Daily | Once a day at a time you set |
| Weekly | Chosen weekdays at a time |
| Monthly | A day of the month at a time |
| Event | When something happens on the server (see below) |
| Manual | Never on its own — you press run, or it fires after a Git deploy |
💡 Tip: All clock times use the server owner's timezone, so set that correctly first (Settings page, Environment tab) and every schedule follows it.
Event triggers
An Event schedule reacts to things that happen, not the clock. The available triggers include:
- Server started, stopped, or crashed
- A backup completed
- A player joined or left
- Server idle for a set number of minutes (1–1440)
- CPU, memory, or disk usage crossing a threshold
- A Git deployment completed
Add tasks
A schedule runs one or more tasks in the order you list them. The types are:
| Task | What it does |
|---|---|
| Command | Send a console command (like say Restarting in 60s or save-all) |
| Power action | Start, restart, stop, or kill the server |
| Backup | Take a backup (see Backups) |
| Delete files | Remove files or folders by path |
| Git sync | Pull your latest code (pairs with Git deploy) |
🎯 Good to know: On the free plan you get the Command task; the other four task types are shown as premium. You can chain several tasks in one schedule, so "warn players, save, then restart" is a single schedule with three tasks in a row.
Online vs offline
Free-plan schedules only run while the server is online — which makes sense, since most of them act on a running server. The Run even when the server is offline toggle is premium; it's what lets a schedule start a stopped server (for example, a daily boot-up).
Edit, pause, or delete a schedule
A schedule isn't set in stone. Open one and you can change its trigger, add or remove tasks, and drag tasks into a different order — the same builder you created it with doubles as the editor.
- Pause it — a toggle turns a schedule off without deleting it. The trigger stops firing until you switch it back on. Handy for silencing the nightly restart during an event, then resuming it after.
- Run it now — every schedule has a run-by-hand button that fires its tasks immediately, whatever its trigger. This is how you test one (see below).
- Delete it — removes the schedule and all its tasks for good. There's no undo, but nothing on your server changes; you're only removing the automation.
🎯 Good to know: Schedules live in the panel, not in your server's files, so a reinstall survives them — reinstalling only touches files, and your schedules are still there, still firing, when the server comes back.
See whether it ran
Guessing whether a 5 AM restart actually happened is no way to run a server, so each schedule keeps its own Logs. Open them to see every execution: when it fired, whether it succeeded or failed, which task ran, how long it took, and the exact error message if something went wrong. This is the first place to look when a schedule doesn't seem to be doing its job.
Get notified when a schedule runs
A schedule can also ping you when it fires. Add a webhook — a Discord webhook URL, or any plain HTTPS endpoint — and choose which events notify you: schedule started, schedule completed, a task completed, or a task failed. A Test button sends a sample message so you can confirm it lands in the right channel before you rely on it.
💡 Tip: The webhook URL has to be HTTPS. A "task failed" alert is the one most people want — it's how you hear about a backup or restart that quietly broke, without watching the Logs yourself.
Three schedules worth copying
1. Nightly restart
A fresh restart clears memory creep and keeps things snappy. Create a Daily schedule at, say, 5:00 AM with one task: Power action → Restart. That's it. Add a Command task before it (say Nightly restart in 1 minute) if you want to warn players first.
2. Back up, then restart
Chain two tasks so you always have a nightly snapshot. Create a Daily schedule and add, in order:
- Backup — name it something like "nightly".
- Power action → Restart.
Tasks run top to bottom, so the backup finishes before the restart begins.
3. Auto-restart on crash
Keep the server up even if it falls over while you're asleep. Create an Event schedule triggered by server crashed, with one task: Power action → Start. Now a crash is followed immediately by a boot instead of hours of downtime. (This one is premium in practice — it needs a power task and a server that's just gone offline; premium also has dedicated crash-detection settings on the Settings page.) Minecraft owners: pair this with the nightly restart above and your server mostly looks after itself.
Verify it works
The Manual type — and the run-by-hand option on any schedule — is the fastest way to test. Run the schedule yourself once and watch the tasks fire in the console, then check the schedule's Logs to see the run recorded. If it does what you expect by hand, it'll do the same on the trigger, so you're not left guessing until 5 AM.
Troubleshooting
- A timed schedule fired at the wrong hour — the times follow the server owner's timezone; set it on the Settings page (Environment tab).
- My schedule never ran — on the free plan it only runs while the server is online, and only the Command task is available. Check both.
- The task after a power action didn't happen — restarts and stops take a moment; remember tasks run in the order listed, and give a power action room before the next task.
- Git sync did nothing — the repo has to be linked first on the Git page; see Deploy your code with Git.