Setting the schedule

The schedule answers one question: when should this run? You build it in the Schedule dialog, and the dialog writes back in plain language what you have built so far — "Every day at 08:00, 16:00, Europe/Kyiv" — rebuilding that sentence on every click. Read it before you save: it is the quickest way to catch a schedule that says something other than what you meant.

One rhythm at a time

A schedule follows one of three rhythms, and they are mutually exclusive.

Daily — every N days, at the hours you choose.

Weekly — the weekdays you choose, every N weeks, and, if you want, only in certain months. Leave the months empty and it runs all year round.

Monthly — the months you choose, every N months, and a rule for the day: a fixed day of the month, a day counted back from its end, or the Nth weekday.

So "Mondays and Wednesdays, in August and September, every second week" is a single weekly schedule. Weekdays and a day-of-the-month rule, on the other hand, do not combine — they belong to different rhythms, and you pick the one that describes yours.

Hours, not minutes

You choose hours, one or several, and at least one is required — the app will not save a task without it. An hour is also as fine as a schedule gets. Work that has to happen every few minutes is not work for a scheduled task.

The hours are the warehouse's

A schedule carries a time zone, shown with its offset, and its hours are read in that zone. The zone appears in the plain-language description as well, so in a company with sites in several zones it is clear whose morning the task means.

A window, if you need one

A schedule can be given the dates it starts and stops being valid, and the date its "every N" counts from. Leave them alone and the task simply runs from now on.