Run Flows on a schedule

A schedule runs one Flow, on its own, across a tag or a folder of profiles. It is how nightly warm-ups and hourly checks get done without you clicking anything.

Part of Pro, Team and Custom.

LoginDeck has to be open

Schedules are a timer inside the app, not a Windows task. Nothing fires while LoginDeck is closed or the computer is asleep. On Windows, closing the main window quits the app — so leave it open (minimised is fine) on the machine that should run the job. On a Mac, closing the window leaves LoginDeck running in the Dock; it keeps firing until you quit it.

⏰ Create one#

In the left sidebar, under Operate, click Flows, then Open on the Flow.
In the toolbar, click Schedule…. The dialog is titled Schedule "{flow name}".
Pick a When:
- Every day at a time — then a Time (02:00 by default).
- Every so many minutes — then Every {n} minutes, from 1 minute up to a week.
- Once, at a time — then a date and time. Left blank, it is an hour from now.
Pick a Run on: Every profile with a tag or Every profile in a folder, then choose the tag or folder.
Set Run at once (1–20, default 3) and tick headless if you do not want windows.
If the Flow asks for inputs, fill them in under Each run will use these: — they are answered once and reused every time.
Click Create. The toast says Scheduled.

Daily times use this computer's clock, not the profile's timezone.

🗂️ See, pause and delete schedules#

On the Flows page, click Schedules. Each row has:

a switch to turn it off and on,
the Flow's name,
a line reading {cadence} · {target} · next {when} · last: {ok} ok, {failed} failed,
Run now, which fires it immediately (Started on {n} profiles, or Nothing matched),
✕ to delete it.

There is no edit. To change a time or a target, delete the schedule and create it again.

🔁 How a scheduled run behaves#

It runs as a batch, exactly like Run on many… — your Run at once number is the concurrency.
self-heal is on and cannot be turned off here, so an unattended run can spend AI actions repairing a step. See LoginDeck AI actions.
It never stops to ask you anything; nobody is at the keyboard. A failure is recorded as a failure.
The browser closes at the end of each profile's run.
The tag or folder is looked up at the moment it fires, so a profile you tagged this afternoon is included tonight, and a deleted profile drops out by itself.
Results land in Run history and in the row's last: line.

A run missed while the app was closed fires once at the next launch — not once per night you missed.

💻 Schedules stay on this computer#

Schedules are deliberately not synced. If they were, two computers signed into the same account would both fire the same nightly job on the same profiles and fight over them. The Flow syncs; the decision to run it here does not. Want it on two machines? Create it on each — and point them at different tags so they are not opening the same profile.

ℹ️ Good to know#

A schedule is named after the Flow as it was called when you made it. Renaming the Flow does not rename the schedule.
Delete the Flow and the schedule keeps firing and records a failure. Delete the schedule too.
An empty tag or folder records no profiles matched.
A profile that is open on another computer, or already running, is skipped as a failure for that run — the rest carry on.
Nightly warm-ups are the common case: add the Warm up: browse like a person template, tag your new profiles, and schedule it. See Warm up new profiles.
Want your own timing rules, or a run triggered by something else? Drive it from a script with the local API. LoginDeck still has to be open for that too — the browsers it opens are on this machine.