Schedules
Schedules automate work on your server. Each schedule combines triggers (when it fires), an optional pre-condition (checked right before it runs), and an ordered list of actions (what it actually does). The subtitle shows your usage against the server's feature limit, e.g. "1 of 15 maximum schedules created."

The list shows each schedule's name, Last Run, Last Failure, Status (Active or Inactive), and Created timestamps. Click a row to open the schedule, or right-click it for Run Now, Export, Duplicate, and Delete. Run Now is disabled while the schedule is disabled, and Duplicate once the server has reached its schedule limit.
View Calendar opens the Upcoming Runs Calendar, which plots upcoming cron runs in a day, week, or month view. Click an entry to jump to its schedule.

INFO
What a subuser can do here is controlled by the schedules permission group. See Schedules in the Permissions Reference.
Creating a Schedule
Click Create. A schedule starts with a Schedule Name, an Enabled toggle, and any number of triggers added via Add Trigger. Saving takes you straight to the schedule's page, where you add actions. The same form opens later via Edit on the schedule's page.

A disabled schedule ignores its triggers and can't be run manually until re-enabled; the panel refuses with "cannot trigger a disabled schedule".
Changing a trigger's type in the form resets that trigger's fields to the new type's defaults, so nothing from the previous type is carried over.
Triggers
A schedule runs whenever any one of its triggers fires.
| Trigger | Fires |
|---|---|
| Time Interval (Cron) | On a time schedule, in the server's timezone |
| Power Action | When a Power Action (Start, Stop, Restart, Kill) is requested |
| Server State | When the server reaches a Server State (Running, Offline, Starting, Stopping) |
| Backup Status | When a server backup reaches a Backup Status (Starting, Finished, Failed) |
| Database Backup Status | When a database backup reaches a Backup Status (Starting, Finished, Failed) |
| Schedule Completion | When another Schedule finishes, filtered by Completion Status (Successful or Failed) |
| Resource Usage | When a Metric (CPU Usage, Memory Usage, Disk Usage) passes a threshold continuously For (seconds) |
| Console Line | When the console prints a line matching Line Contains (optionally Case Insensitive), with the line optionally stored into a variable via Output into |
| Crash | When the server crashes |
The Resource Usage trigger takes its value the same way as the Resource Usage condition, including % of limit.
Since Panel 1.2.7, adding a Console Line trigger needs the control.read-console permission. Without it, saving fails with "unable to create schedule trigger that requires permission: control.read-console" (or "unable to update ..." when editing).
Cron Triggers
By default the cron trigger uses friendly controls: pick how often it Runs (Every few minutes, Every few hours, Daily, Weekly, Monthly) plus the matching interval, weekday, day, and At time fields. A plain-language description of the resulting schedule is shown underneath, along with a "Times use the server timezone" hint naming the zone (or UTC).
Flip Edit as cron expression to write the expression yourself; clicking the field opens a small per-segment editor.
With Weekly, or with a cron expression, an Every (weeks) field (1 to 52) lets the trigger fire only every second, third or later week. Above 1, an Aligned to the week of date picks which weeks count, filled with today's date in the server's timezone the first time the interval goes above 1. Weeks are counted in seven-day blocks from that date, so they start on its weekday rather than on Monday. The description underneath gets ", every 2 weeks" (or similar) added, and the calendar and the cron card's next run follow the interval. Switching Runs away from Weekly sets it back to 1.
The week interval needs Panel and Wings 1.2.8 or newer. Wings 1.2.7 and older ignore it and run the trigger on every match of the expression, as if Every (weeks) were 1.

WARNING
Calagopus cron expressions put seconds first: second minute hour day month weekday. So 0 0 0 * * * is daily at midnight. Classic five-field crontab lines work as-is (5 to 7 fields are accepted); the seconds field only applies when present.
Bulk Actions
Select rows with their checkboxes, by dragging across them, by Shift-clicking a second checkbox for a range, or with Ctrl+A (Esc clears); only rows on the current page are selected. The action bar then offers:
| Action | Notes |
|---|---|
| Run Now | Triggers the selected schedules, either Run now (check conditions first) or Run now (ignore conditions). Disabled schedules are skipped. |
| Enable / Disable | Each only touches the schedules not already in that state; the buttons show how many that is. |
| Delete | Deletes them after a confirmation. |
Selecting needs schedules.update or schedules.delete. Each action reports how many items it changed, skipped or failed in a toast.

The Schedule Page
Opening a schedule shows its name with an Active/Inactive badge, a Run Now button, and Edit. Two cards show Last Run and Last Failure ("Never" until they happen). Below that are three tabs: Actions, Conditions, and Triggers.
Run Now offers two modes: Run now (check conditions first) and Run now (ignore conditions). The button is disabled while the schedule itself is disabled ("Cannot run a disabled schedule").

Actions
The Schedule Actions tab is the heart of a schedule: an ordered list of steps. Add one with Add Step (or Create First Step on an empty schedule), drag the handle to reorder, and click a step's chevron to expand its full configuration. The maximum number of steps per schedule is a panel-wide setting, Max Schedule Steps under Settings > Server. Once a schedule has that many steps, Add Step and Create First Step are disabled with the tooltip "This schedule is limited to N steps."
Each step's menu offers Edit, Duplicate, and Delete. Duplicate is disabled at the step limit too, and duplicating an If step needs two free slots rather than one. While the schedule executes, the current step shows a Running badge; a step that failed on the last run shows a red warning icon with the error message.
Steps are picked from a searchable Action Type list, organized into five groups.

Most steps have an Ignore Failure switch to let the schedule carry on if that step fails. Long-running operations (backups, file copies, archives, downloads) additionally have Wait for Completion (called Run in Foreground before Panel 1.2.8). With it on, the schedule waits for the operation to finish and a failure counts as a failed step. With it off, the step runs in the background: the next step starts right away and failures are not reported. Each such step shows a Waits or Background badge in the step list.
Server
| Step | What it does | Key fields |
|---|---|---|
| Send Command | Send a command to the server console. | Command |
| Send Power Signal | Start, restart, stop or kill the server. | Power Action |
| Wait for Server State | Wait until the server reaches a power state. | Server State, Timeout (milliseconds) |
Backups
| Step | What it does | Key fields |
|---|---|---|
| Create Backup | Create a backup of the server files. | Backup Name (auto-generated if left empty), Backup Group, Ignored Files, Output Backup UUID Into, Wait for Completion |
| Restore Backup | Stop the server and restore a backup of the server files. | Backup to Restore, Delete all files before restore, Restore startup settings |
| Delete Backup | Delete a backup selected by the backup selector. | Backup to Delete |
| Move Backup | Move a backup selected by the backup selector into a backup group. | Backup to Move, Target Backup Group |
| Create Database Backup | Create a backup of a managed database. | Managed Database, Backup Name, Backup Group, Output Backup UUID Into, Wait for Completion |
| Restore Database Backup | Restore a database backup into a managed database. | Database Backup to Restore, Only Consider Backups From, Restore Into |
| Delete Database Backup | Delete a database backup selected by the backup selector. | Database Backup to Delete, Only Consider Backups From |
| Move Database Backup | Move a database backup selected by the backup selector into a backup group. | Database Backup to Move, Only Consider Backups From, Target Backup Group |
The backup selector picks the Latest Backup, the Oldest Backup, a Specific Backup (UUID), or one By Name (optionally matching the oldest instead of the newest), and can be narrowed to a backup group.
The four database steps use the same selector, restricted to database backups. Each has an Only Consider Backups From picker that narrows the selector to dumps taken from one managed database; leave it at Any managed database to consider every dump on the server.
Restore Database Backup also has Restore Into, which defaults to "The database the backup was taken from": set it when that database no longer exists, or to copy data into a different managed database running the same engine.
WARNING
Restoring stops the server and overwrites its files; avoid combining Restore Backup with power or server state triggers that could re-trigger the schedule. Restore Database Backup overwrites the contents of the target database and does not wait for the import to finish, so later steps can run while it is still in progress. Delete Backup and Delete Database Backup permanently delete the backup and its files on the node, and fail if the selected backup is locked.
Files
| Step | What it does | Key fields |
|---|---|---|
| Create Directory | Create a new folder in the server files. | Root Path, Directory Name |
| Write File | Write or append text to a file. | File Path, Content, Append to File |
| Copy File | Copy a file to a new location. | Source File, Destination, Wait for Completion |
| Delete Files | Delete files or folders, or move them to the trash. | Root Path, Files to Delete, Move to Trash |
| Rename Files | Rename or move files. | Root Path, file pairs (from / to) |
| Compress Files | Compress files into an archive. | Root Path, Files to Compress, Archive Format (.tar family, .zip, .7z), Archive Name, Wait for Completion |
| Decompress File | Extract an archive into a folder. | Root Path, File, Wait for Completion |
| Pull File | Download a file from a URL into a folder. | File URL, Root Path, File Name (derived from the URL or the response when left empty), Use Response File Name, Wait for Completion |
Move to Trash on a Delete Files step is off by default, so a step deletes permanently unless you turn it on. It only takes effect while the trash is enabled for the server; with the trash off, or on a node older than Wings 1.2.6, the files are deleted permanently. Files inside a mount are always deleted permanently. When the trash is used, the step is logged as server:file.trash instead of server:file.delete, even if some of its files were on a mount and deleted permanently.
Startup Settings
| Step | What it does | Key fields |
|---|---|---|
| Update Startup Variable | Change the value of a startup variable. | Environment Variable, Value |
| Update Startup Command | Change the command used to start the server. | Startup Command |
| Update Docker Image | Change the Docker image the server runs in. | Docker Image |
Advanced Logic
| Step | What it does | Key fields |
|---|---|---|
| Sleep | Wait for a set amount of time before continuing with the next action. | Duration (milliseconds), up to 24 hours |
| Ensure | Stop the schedule here unless a condition is true. | Condition builder |
| If / Else If / Else / End If | Run the following steps only when a condition is true, until Else/End If. | Condition builder on If and Else If |
| Exit | Stop the schedule here, marking the run as successful or failed. | Mark run as successful |
| Format | Build a text value from variables and store it in a variable. | Format String (wrap variables in {{...}}), Output into |
| Match Regex | Extract parts of a text value using a regular expression. | Input, Regex, Outputs (one variable per capture, added via Add Output) |
| Wait for Console Line | Wait until the server console outputs a matching line. | Line Contains, Case Insensitive, Timeout (milliseconds), Output into |
| HTTP Request | Send an HTTP request, for example to a webhook. | See below |
Creating an If step automatically adds its End If, and steps inside the block are indented in the list. The menu on an If or Else If step offers Add Else If and Add Else to grow the block. The editor warns if a block is broken: "An "If" block is missing its "End If"" or an Else/Else If/End If exists "without a matching "If" before it".
Variables
Many step fields accept either plain text or a variable; the icon at the field's right edge toggles between the two ("Use a variable instead of plain text"). Variables are produced by outputs elsewhere in the schedule: the Console Line trigger's Output into, Match Regex captures, Format, the UUID outputs of Create Backup and Create Database Backup, and the HTTP Request outputs. A variable holds up to 16 KiB.
The editor checks every variable a step or condition reads against where it gets set, following the order of the steps and the If blocks. A step with a problem gets a yellow warning icon (hover it for the details), the step dialog shows the same warnings while you edit, and a warning under the pre-condition covers the Conditions tab:
| Warning | Means |
|---|---|
| The variable "x" is never set by this schedule, so it will not resolve. | No trigger or step writes it at all, usually a typo. |
| The variable "x" is not set by a trigger or an earlier step at this point. | It is written, but only by a later step. |
| The variable "x" is only set on some runs, for example inside another branch, by one of several triggers or by a step that may fail. | Whether it exists depends on how the run went: it is set inside an If branch, by only some of the schedule's triggers, or by a step with Ignore Failure on. |

The warnings don't stop you from saving. A Variable Exists condition is the way to handle a variable that is only set on some runs.
HTTP Request
The most configurable step:
| Field | Notes |
|---|---|
| Method | GET, POST, PUT, PATCH, DELETE, or HEAD. |
| URL | The request URL. |
| Headers | Name/value pairs via Add Header, up to 32. |
| Body | Optional. |
| Timeout (milliseconds) | Up to 60 seconds. |
| Ignore Error Status Codes | Keeps an error response from failing the step. |
| Output Status Code Into / Output Response Body Into | Store the response into variables for later steps. |
INFO
For admins: HTTP Request steps are sent from the node, and Wings enforces node-level limits, by default 5 requests per 60-second window per server, a 16 KiB captured-response cap, private CIDR ranges blocked, and an option to disable the step entirely. See the Wings configuration reference.
Conditions
The Schedule Pre-Conditions tab defines a condition checked before the schedule runs (unless triggered with Run now (ignore conditions)). Build it with the Condition Type select; the combinators AND (All must be true), OR (Any must be true), and NOT (Must not be true) nest further conditions via Add Condition, up to three levels deep.

| Condition | Checks |
|---|---|
| None | Nothing, always passes |
| AND (All must be true) | Every nested condition |
| OR (Any must be true) | At least one nested condition |
| NOT (Must not be true) | Inverts its nested condition |
| Server State | The server's current power state |
| Uptime | Server uptime against a Comparator and Value (seconds) |
| Resource Usage | A Metric (CPU Usage in percent, Memory Usage or Disk Usage as a size, or any of them as % of limit) against a Comparator and value; see Resource Usage Values |
| File Exists | Whether a File Path exists |
| Variable Exists / Variable Equals / Variable Contains / Variable Starts With / Variable Ends With | A schedule variable against a value |
Comparators are Smaller than, Smaller than or equal to, Equal to, Greater than or equal to, and Greater than. The same builder appears inside Ensure, If, and Else If steps.
Resource Usage Values
The unit select on the right of the Value field decides what the number means. For CPU Usage, % is absolute: 100% is one full CPU core, whatever the server's limit. For Memory Usage and Disk Usage you pick a size unit.
Since Panel 1.2.9, every metric also offers % of limit, which compares against a share of the server's own limit (0 to 100). Wings works the percentage out from the limit in effect at the time, so the condition keeps matching the same share when an admin changes the limit later. For CPU on a server without a CPU limit, the percentage is taken against all of the host's cores. Since Wings 1.2.10 the CPU percentage always uses the server's configured limit; Wings 1.2.9 used the lifted limit while a startup boost was running. Memory and disk without a limit have nothing to compare against, so % of limit is disabled there, and a saved one never matches ("This server has no limit for this resource, so a percentage will never match"). Switching between % of limit and an absolute unit converts the number using the current limit. Cards show the value as, for example, 80% of limit.
WARNING
% of limit needs Wings 1.2.9 on the node. Older Wings ignores the setting and reads the number as an absolute value, so 80 becomes 80% of one core for CPU, or 80 bytes for memory and disk.
Changes here must be saved with Update; navigating away with unsaved changes prompts you first.
Triggers
The Schedule Triggers tab lists each trigger as a card. Cron cards also show the next and last run times. To change triggers, use Edit at the top of the page. A schedule without triggers shows No Triggers here: it never starts on its own and only runs when started by hand.
Import and Export
Right-click a schedule for Export, then Export as JSON or Export as YAML; this downloads the schedule as a file (schedule-<uuid>.json or .yml) that can be imported again, on this server or another one.
Import accepts a .json, .yml, or .yaml schedule file. You can also drag files straight onto the page ("Drop some files here to import them as Schedules"); multiple files import multiple schedules. Imports count toward the schedule limit.
Duplicating and Deleting
Duplicate in the row menu asks for a New Name (prefilled with "(copy)") and creates a copy of the schedule. Delete asks for confirmation and removes the schedule outright.