Scheduler

For account work the hour matters as much as the task. A run at three in the morning local to nobody is a pattern of its own, and a queue of catch-up runs at breakfast is a louder one.

A scheduler is the part that starts a job at an hour you chose instead of at the moment you press a button.

What a schedule points at

A schedule is not a standalone alarm. It names an automation, the profiles it runs over, how often to repeat and how many go at once.

The automation
The flow to run. Without one a schedule is an alarm ringing at nothing.
The profiles
Which profiles it acts on, each checked against the ones you have.
The repeat rule
Daily at a time, weekly on chosen days, or a whole number of hours apart.
How many at once
A handful in parallel, so thirty profiles become a queue and not thirty sign ins in a minute.

Local time is the whole point

Nine in the morning means nine where you are sitting, and it still does after a clock change. The next slot is found by walking calendar days, because twice a year a day is not the length of the one before.

Each schedule remembers the offset it was worked out in, and a different offset at startup makes it recalculate.

Su equipo, ahora mismo

Your time zone: midiendo en su equipo
Hours from UTC: midiendo en su equipo

Leído en su navegador y mostrado aquí. No se envía nada a ninguna parte.

Late slots and missed slots

A slot that has only just passed is still the same run, so a short grace window lets it fire. Later than that it is a different hour of the day, and firing then is what a timetable exists to avoid.

1
You open the lid
The next tick comes around within half a minute of the app being awake.
2
Overdue slots move on
Anything too late to still be itself is walked forward into the future.
3
You are told what was lost
One warning per schedule, naming the automation and how many runs were lost.

Where the clock actually runs

Your account stores schedules so they travel between your machines, and it runs none of them. A run needs the cookies, the fingerprint and the proxy of a profile, and all of those sit on your computer.

A schedule made in the app works here from the moment it is saved. One arriving from your account lands not running here until you say otherwise, because two open copies would fire one run twice.

When a due slot turns into nothing

A due slot does not always become a run. Each of these raises a notification and leaves a line you can read next morning.

No active subscription
The slot is passed over and nothing is stored up to happen later.
The previous run is still going
A long run can outlast its own next slot, and it is not sent into its own profiles.
The profiles are already open
Live windows are left alone rather than reopened over your work.
More profiles than the plan covers
The list is trimmed, and the cut rotates so the same tail is not dropped every time.

Often confused with

Cron on a server
A server timetable runs without you. This one runs while the app is open, because the browser it needs is on your desk.
A queue
A queue starts work as soon as a worker is free. A timetable makes work happen at a chosen hour and not before.
The daily pace counter
That one counts pages opened today and paints a bar, and it never blocks anything, so the decision stays with you.

What this does not do

Nothing runs while the app is closed or asleep. No background service is installed, so a closed laptop misses its slot.
Missed slots are never replayed. You are given a count and a warning instead, because a queue of catch-up runs at breakfast is the burst a timetable exists to avoid.
Repeat rules are fixed: daily at a time, weekly on chosen days, or a whole number of hours apart. There are no cron expressions, no one off dates and no interval shorter than an hour.
A schedule always needs an automation, and it spreads starts only by how many run at once. There is no rule that merely opens profiles and leaves them sitting there.

Check it

The rules, the file that holds them and the stand that runs them.

The repeat rules, the grace window and the walk to the next slot: apps/desktop/src/lib/schedules.js
Local time survives a clock change, and missed slots are counted rather than replayed: apps/desktop/test/schedule-runs.js
The tick, the plan quota across it and every reason a slot is skipped: apps/desktop/src/main/main.js
A schedule arriving from your account lands off here and can be turned on: apps/desktop/test/расписание-включается-здесь.js

Questions

Can two of my computers fire the same schedule?: No. A schedule reaching a second machine arrives marked not for here, with a button to turn it on, because one account arriving twice from two places is a pattern worth avoiding.
Does starting a run by hand move the next time?: No. It starts the automation immediately and leaves the timetable alone, so pressing it at eight does not cancel the nine o'clock run.
What happens when the laptop changes time zone?: The next time is worked out again in the zone you are in now. A slot already due survives that recalculation, so a move never swallows a run due this minute.
How often does it look at the clock?: Twice a minute, inside the app. Anything finer would spend battery where a minute of precision means nothing.
What is written down after a run?: A sign rather than a sentence, turned into words in the language of whoever is reading. A skip is stored apart from a result: a slot that never ran is not a run with a poor outcome.

Next to this

Put the nightly run on a timer

Build the automation once, pick the profiles, choose an hour. The app does the rest while it is open.

Download ARMANOS Scheduler