Block reference / Workflow

Run on profiles

Start another workflow on other profiles, a few at a time, and optionally wait for the results.

Only inWarpX Browser

Run on profiles starts another workflow on the profiles you list, or every profile in a group, the way Run automation on the Profiles page does: each profile opened, the run monitor kept up to date. Combined with List profiles it lets one workflow decide which accounts need work and hand that work out. It can carry on at once, or wait for every run to end and leave by the fallback output when any failed.

The Run on profiles block's settings, filled in as in the example below.

Settings

Description

A note shown on the block in the canvas.

ExampleWarm up 3 at a time
Workflow

The workflow to run, from your Automations list. The one you are editing is left out: a workflow cannot start itself. A workflow that is turned off is refused when the block runs.

ExampleWarm up
Profiles

These profiles (the default) or Every profile in a group.

ExampleThese profiles
These profileswhen Profiles is These profiles

Ids or names separated by commas or lines, or a variable holding what List profiles found. Up to 500.

Example{{variables.profiles}}
Every profile in a groupwhen Profiles is Every profile in a group

The group whose profiles to run on, picked or typed.

ExampleTikTok VN (20)
At once

How many profiles run at the same time, from 1 to 20. Your plan's limit on browsers open at once also applies.

Example3
Seconds between starts

A pause between one profile starting and the next, up to 10 minutes. 0 starts them together.

Example20
Open as

A window (the default), Minimised or No window (headless).

ExampleMinimised
Variables

A JSON object every run starts with — what Run automation would ask for as parameters, since nobody is there to answer them. {{references}} work. Anything but an object fails the block with "Variables must be a JSON object".

Example{"keyword": "{{variables.keyword}}", "minutes": 15}
Close each profile when its run ends

On by default.

ExampleChecked
Show the run monitor

Bring up the run monitor when the runs start.

ExampleUnchecked
Wait for them to finish

On by default: the block ends when every run has ended. Off, it carries on as soon as the runs are queued.

ExampleChecked
Stop waiting after (minutes)when Wait for them to finish is on

0 to wait as long as it takes, up to 24 hours. When the time runs out the block stops waiting; the runs still going are left running.

Example60
Assign to variable

On by default.

ExampleChecked
Variable namewhen Assign to variable is on

The variable that gets the result. The default is runResult.

ExamplerunResult

Every block also has the shared block settings — a description, Disable block and what to do on an error. Fields that take text accept data from earlier blocks.

What it hands on

Two outputs. The variable holds runId, workflowName, finished, timedOut, total, succeeded, failed, cancelled and items — one per profile with profileId, profileName, status (success, error, cancelled, or queued / running when not waited for) and message. Waiting, the run leaves by the bottom (fallback) output when any run failed or the wait ran out, if that output is connected; otherwise, and when not waiting, by the top one. The log shows 2 of 3 succeeded · 1 failed.

Example: Warm up the accounts tagged "need-warmup", 3 at a time

  1. Start
  2. List profiles
  3. Run on profiles
  4. Update profile
Where Run on profiles sits in the example workflow.
  1. Add a List profiles block with Tags need-warmup and State Closed; leave Variable name as profiles.
  2. Add a Run on profiles block. Set Workflow to Warm up, Profiles to These profiles with {{variables.profiles}}.
  3. Set At once to 3, Seconds between starts to 20 and Open as to Minimised.
  4. Set Variables to {"minutes": 15}, which Warm up reads as {{variables.minutes}}.
  5. Leave Wait for them to finish on, with Stop waiting after (minutes) 60.
  6. Connect the fallback output to a Notification saying Warm-up: {{variables.runResult.failed}} failed.
  7. Connect the top output to an Update profile block on {{variables.profiles}} that removes the tag need-warmup.

Good to know

  • Before an installed workflow can start runs, you are asked. The first time a workflow that was not edited on this computer runs a block that changes profiles — Create profile, Update profile on profiles other than the running one, Set proxy, Move to group, Open profile, Close profile, Run on profiles — WarpX Browser shows a window listing what each of those blocks will do and asks you to allow it before the run starts. Blocks you set up yourself in the editor are approved as you edit them, so your own workflows never ask. Changing such a block's settings asks again. This protects you from an automation you installed, from the Appstore or a file, quietly moving all your profiles onto someone else's proxy.
  • A run started by this block cannot start more runs: a Run on profiles block inside it fails with "A run started by a Run workflow block cannot start more runs". Otherwise a workflow run on fifty profiles could start fifty more each.
  • The profile running this block is never one of the targets — the block fails with "The profile running this workflow cannot be one of the profiles it starts". Profiles already running a workflow are refused too: "Already running a workflow:" followed by their names. In both cases nothing is started.
  • Each run that has not finished 30 minutes after it started is stopped and counted as failed. When the workflow with this block itself runs inside a batch run — Run automation, a schedule, or another Run on profiles — that run is stopped 30 minutes after it started too, so the block stops waiting shortly before that limit and its log line says so. The runs it started carry on.
  • The fallback output is taken for failed runs, not for cancelled ones.
  • A profile, group or proxy is found by its id, or else by its name ignoring case. When two have the same name the block fails with "2 records are named … — use the id instead"; one that is not there fails with "No profile …".
  • Needs the WarpX Browser desktop app, where the profiles are. Elsewhere the block is not in the block list, and a workflow that has it fails with "Profile and group blocks need the WarpX desktop app".
  • On an Appstore listing, a workflow with this block shows Starts your other automations on other profiles.

See also

  • List profiles — The profiles in a group, with a tag, open or closed — as records or as ids.
  • Execute workflow — Run another automation from this one and wait for it to finish.
  • Open profile — Launch profiles that are closed, as their Open button does.