Block reference / General

Wait connections

Holds branches that run side by side until they have all arrived.

In both appsWarpX BrowserWarpX Phone

When one block's output is connected to several blocks, those branches run at the same time. Wait connections is where they meet again: each branch stops here until every connected branch has arrived, or until the timeout runs out. Use it when the next step needs results from all of them.

The Wait connections block's settings, filled in as in the example below.

Settings

Description

A note shown under the block's name on the canvas. It has no effect on the run.

ExampleWait for both lookups
Timeout (milliseconds)

The longest a branch waits here for the others. When the time is up, the branch carries on without them. It does not fail.

Example15000
Only continue a specific flow

When on, only the branch you pick below carries on past this block. The other branches stop here once everything has arrived.

ExampleChecked
Select flowwhen only continue a specific flow is on

The branch that carries on. The list shows the blocks connected into this one, with their description in brackets.

ExampleHTTP request (Get address)

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

Nothing of its own. The block leaves by its single output, once per branch that carries on.

Example: Look up two values at once, then fill in a form

  1. Start
  2. HTTP request
  3. HTTP request
  4. Wait connections
  5. Forms
Where Wait connections sits in the example workflow.
  1. Connect the Start block's output to two HTTP request blocks. Give them the descriptions Get address and Get phone. Each saves its answer to a variable.
  2. Add a Wait connections block and connect both HTTP request blocks into it.
  3. Double-click it, set Timeout (milliseconds) to 15000 and tick Only continue a specific flow.
  4. In Select flow, choose HTTP request (Get address).
  5. Connect its output to a Forms block that types {{variables.address}} and {{variables.phone}} into the page.

On WarpX Phone

  • On WarpX Phone, branches in the same run drive the same phone, and a phone carries out one command at a time. Phone blocks on side-by-side branches take turns rather than act together; branches that do not touch the phone, such as an HTTP request request, still run alongside.

Good to know

  • Without Only continue a specific flow, every branch that arrives carries on. The blocks after Wait connections then run once for each incoming branch. Tick the box when they should run once.
  • Select flow lists the connections that existed when you opened the block. If you connect another branch later, open the block again and check the choice.
  • If the chosen flow is no longer connected to the block, the run fails with No specific flow selected.
  • Branches in the same run drive the same profile and the same page. Run page actions one after another, and keep side-by-side branches for work that does not touch the page, such as HTTP requests.

See also

  • HTTP request — Sends an HTTP request to a URL and can store the response.
  • Delay — Pauses the run for a set number of milliseconds before the next block.
  • Conditions — Send the run down one of several paths, depending on values, page elements or code.