All chapters

Schedules

A schedule is a named definition of when something is active: business hours, a maintenance window, a closure. Rules test a schedule as a condition (“only when it is not active”) or start when it switches on or off. It replaces copying the same time conditions into every rule, and a change is made in one place.

What a schedule contains#

Weekly windows: days of the week with a start and an end time. A window that wraps midnight belongs to the day it starts on.
One-off periods: a date and time range, for a holiday, a shutdown or an event.
Each entry either includes or excludes time. An exclusion always wins, so “business hours, except these holidays” is one schedule.
A time zone of its own, or, when unset, your organisation's. Schedules are daylight-saving safe: entries are turned into exact instants, so the hour that is repeated or skipped in spring and autumn is handled correctly.

The editor previews the next 14 days of the schedule as you edit, before you save. A schedule can hold 100 entries and an organisation 200 schedules.

Using a schedule#

As a condition#

The Schedule condition is true while the schedule is active, or while it is not, as you choose. A schedule that is missing, belongs to another organisation or has not been chosen makes the condition false either way; Huntress never guesses.

As a trigger#

Choose Schedule as the WHEN of a rule and pick whether it starts when the schedule starts, ends or both. The rule runs at the moment of the switch, with the schedule's name as its source and no sensor. Typical uses: turn lights on at opening time and off at closing time, post a webhook when the working day starts, open an incident if a door is open at the moment the shop closes.

To get a new incident every day, turn on resolve when the source restores: the end of the schedule closes yesterday's incident, so the next start opens a new one. Without it, the next start joins the incident that is still open.

A rule that starts on a schedule may not read an event (the editor refuses such a combination), because there is no event at the switch.

Behaviour worth knowing#

A switch missed while the server was down is replayed after a restart only when it is less than Schedules:CatchUpMinutes old (5 by default; 0 replays nothing). A switch is never run twice.
Saving a changed definition or time zone never counts as a switch.
A schedule that a rule uses cannot be deleted; the page tells you which rule. A silently false condition would be an alarm that never fires.
Owners and Admins edit schedules; Viewers see the list.

Rolling backA server that is rolled back to a release older than schedules skips the rules that use them (it logs a warning) instead of failing. Re-check those rules after a rollback.

Not included: importing public holidays, monthly recurrence, or a time zone per place.