Running one workflow across many profiles

What a batch run actually does

Pick the profiles — by hand, or a whole group — choose the workflow, and WarpX Browser starts them in their own browsers. Up to twenty run at the same time; the rest queue and start as places free up. You can watch each one, or run them hidden or headless if you would rather have the machine back.

Each run is separate all the way down. Separate cookies, separate storage, separate fingerprint, separate proxy if the profile has one. A workflow that signs in signs into that profile’s account, not a shared one.

Giving each profile its own data

Most batch jobs need a row per profile: an account, a search term, a target URL. Two ways to do it:

• A table. Keep the rows in the workflow’s own table and loop over them.
• Google Sheets. Read the sheet at the start of the run, filter to the rows for this profile, and append results at the end.

Both are blocks, so no code is involved. If a run has to answer a question you cannot know in advance, a parameter prompt can ask for it in the profile’s own window.

When one of forty fails

It will. A page loads slowly, a selector moves, an account asks for a code. Every run keeps its own log naming the block it stopped on, so the question is never “which of these forty went wrong” — it is which block, on which profile.

Fix the block and start that run again from it rather than from the top, which matters when the first ten steps were a login you do not want to repeat.

Leaving it to run

A workflow can run on a schedule: once at a time you choose, at an interval, daily or weekly, over a group or a hand-picked set of profiles. Tasks run while WarpX Browser is open — it can sit in the tray with its window closed, but a machine that is asleep is a machine that is not running your workflow.

Start smaller than feels necessary. Two profiles, watched, is a better first run than forty headless — the mistakes you find in the first two are the mistakes all forty would have made.