Scheduling and unattended operation

2 min read · updated 23 Jul 2026

Each job uses one of two schedule modes, set on its Schedule tab.

Every N minutes

Paced from the last completed run, not from when AUTO was switched on — so toggling AUTO doesn't restart a job that has only just finished. A job that has never run is due immediately.

At set times

Pick any combination of days, hours and minutes past the hour. The job fires at every combination of the three, which covers the patterns a station actually needs:

What you wantDaysHoursMinutes
Five to every hourAllAll55
On the hour and half pastAllAll0, 30
Nightly at 03:00All030
Weekday breakfast and driveMon–Fri06, 180
Weekend overnights onlySat, Sun00050

Quick buttons set days to All / Mon–Fri / Sat–Sun, and hours to All / 06–18 / None.

CHECK THE PREVIEW BEFORE SAVING. A live preview under the grid describes the schedule in plain English, gives the number of runs per week, and lists the next four fire times. Ticking every hour and every minute is easy to do by accident, and the run count is where you'll notice.

How schedules appear in the job list

Each pattern is summarised: Every hour at :55, Daily at 03:00, Weekdays 06:00, 18:00, Weekends 00:00, 00:30, 01:00 +3 more.

Upgrading from an earlier version

Older configurations migrate automatically. A job previously set to "daily at 03:15" becomes every day, hour 03, minute 15 — and still reads as Daily at 03:15. Nothing needs reconfiguring.

Running unattended

The schedule lives inside the application, so the application has to be running. Two ways to arrange that:

  • Put a shortcut in shell:startup and tick Start the schedule when the app opens.
  • Or ignore the built-in scheduler and let Windows Task Scheduler launch the executable — it will start, mirror, and sit in the tray.

Closing the window keeps the app running in the system tray so schedules keep firing. To quit properly, use the tray icon's right-click menu.

CHECK IT IS STILL RUNNING: An unattended mirror that has quietly stopped looks exactly like one with nothing new to fetch. Glance at the Last result column periodically rather than assuming silence means success.

Global preferences

AUTO on launch, close-to-tray behaviour and protocol logging live in the app menu and apply to every job.

Was this page helpful?

Still stuck? Ask in the community forum .