Scheduled tasks

Some maintenance is better done on a timer than remembered. CloudPilot can run two things on a schedule.

What can be scheduled#

Creating one#

A schedule needs:

• A name — for your own reference.
• A type — one of the two above.
• An interval, in minutes. Anything from 1 minute to 7 days (10080 minutes).
• The servers it applies to.

A database backup also needs to know which destination and which database to back up.

Picking an interval#

The interval is how long CloudPilot waits between runs, not a clock time. A 1440-minute backup runs once a day, but not at a fixed hour — it drifts with whenever the last run finished.

Two rules of thumb:

• Backups: match the interval to how much work you can afford to lose. Daily is a reasonable default; hourly if the data changes constantly.
• Agent updates: weekly is plenty. The agent does not change often, and an update restarts it, which briefly takes the server offline in the panel.

Turning one off#

Schedules can be disabled without deleting them, which is what you want while debugging — a disabled schedule keeps its settings and its history.

Seeing what ran#

Each schedule records its last run and when it is next due. Failures are worth routing to a notification channel: a backup schedule that has been failing quietly for a month is worse than one you never created, because you thought you were covered.

What is not scheduled#

Deploys are not on this list, deliberately. A deploy replaces what is live, and that belongs to a person and a moment — either someone presses the button, or a push triggers it through auto-deploy. A timer deploying whatever happened to be on a branch at 3am is not a feature.