Run a Flow on one profile or many
Pick a profile and press Run, or send the same Flow across a list of profiles with up to 20 browsers going at once.
On this page
A run drives a real LoginDeck session: the profile's own fingerprint, proxy, timezone and cookies. Watching one run is the fastest way to see whether a Flow does what you meant.
Part of Pro, Team and Custom.
▶️ Run it on one profile#
- In the left sidebar, under Operate, click Flows, then Open on the Flow you want.
- In the toolbar, choose the profile from the dropdown (its tooltip says The profile this run drives).
- Tick any of the four options beside it — they are explained below.
- Click ▶ Run.
- If the Flow asks for anything, a Run dialog appears — fill it in and click Run.
Unsaved edits are saved before the run starts. No profile picked gets you Pick a profile to run it on.
The four toolbar options#
| Option | Default | What it does |
|---|---|---|
| headless | off | Runs with no window. More detectable — avoid it for anything logged in. |
| keep open | off | Leaves the browser open when the run ends, so you can look at where it got to. |
| self-heal | on | A step that fails is read off the live page and repaired by your AI model on the spot. Costs an AI action. |
| ask when stuck | on | If a run gets stuck past what self-heal can fix, it keeps the browser open and asks you what to do. |
Both of the last two are covered in When a Flow gets stuck.
📜 Reading the run log#
The bar at the bottom opens as Run log. It shows a phase — launching, running, healing, stuck, revising, closing, done, error, stopped — which step it is on, and a tally of steps, skipped steps and repairs. Click any line to select that step on the canvas.
The run opens its own fresh tab and brings it to the front. Stop replaces Run while it is going.
When it finishes you get one of:
- "{flow}" finished — {n} steps
- "{flow}" finished, but {n} optional steps found nothing — it may not have done its job — a step marked carry on if it is not there found nothing. Worth a look.
- "{flow}" failed — {error}. Errors always name the step first, like Click — could not find "Sign in" on this page.
The browser closes at the end unless keep open is ticked. The log may say the browser is taking a while to close — the next run on this profile may have to wait; that is the app making sure two runs do not collide.
👥 Run it on many profiles#
- Open the Flow and click Run on many….
- Set Run at once — how many browsers go at the same time. Default 3, maximum 20.
- Tick headless (no windows) if you want no windows, and leave self-heal on or turn it off.
- Tick the profiles (or use Select all / None), fill in the Flow's inputs once, and click Run.
A sheet titled Running on many tracks it: a progress bar, {done}/{total} done · {ok} ok · {failed} failed · {stopped} stopped · {running} running, and a row per profile showing its current step or its error. Stop all ends the lot.
Things that differ from a single run:
- A batch never shows a stuck card — one question per profile would be chaos. A failure is just recorded as a failure.
- keep open is always off.
- A profile that cannot start (open elsewhere, deleted, locked) is recorded as failed and the queue carries on.
- A repair found on the first profile is saved and used by the profiles still queued.
Nothing ticked gets you Pick at least one profile.
🕘 What ran, and when#
The library's Run history button lists every run — Flow, profile, when, and the result, with a short error and a ✨ Fix button on failures. Click a row to read that run's log. It holds the last 500 runs, counts scheduled, batch and API runs too, and stays on this computer.
🛟 When a run will not start#
| Message | What to do |
|---|---|
| "{flow}" is already running on this profile | One run per profile. Wait for it, or press Stop. |
| this profile is already running without an automation port — stop it first, then start it through the API | You opened the profile by hand. Close that browser window, then run the Flow. (The wording mentions the API even when you pressed Run here.) |
| this profile is open on another computer — run it there, or take it over first | See When someone else has a profile open. |
| automation (API/MCP) is not supported for Firefox profiles yet — run it from the app, or use a Chromium profile | Flows need a Chromium profile: Chrome or Firefox. |
| This profile is locked… | You are over your plan's profile count. See Plan limit messages. |
| fill in {labels} before running | A required input is empty. |
ℹ️ Good to know#
- Screenshots and files a run saves go into that run's own folder; Screenshot and Save to file can store the path in a variable so the log tells you where.
- A run is in memory only. Quitting LoginDeck ends it, and a half-finished run does not come back on the next launch.
- Runs stop themselves after 40,000 steps, with this flow does not reach an End (check the loop wiring).
- To run without being at the keyboard, use Run Flows on a schedule, or start runs from your own script or an AI agent: Get started with the local API.