For each, in parallel
Starts one path per item of a list, all at once, up to 1,000. The paths must meet again at a Wait for paths, which decides when the run carries on.
Kind
control:parallelForEachGroupFlow
Credits0.1 credits
Ports out2
How it looks
Settings
| Setting | Required | What it does |
|---|---|---|
| Listcollection | Yes | Where the list is in the run. |
Ports
| Port | The run leaves by it when |
|---|---|
body | Once per item, each on its own path. Lead them all to one Wait for paths. The canvas calls it each item. |
empty | The list had no items, so no path started. |
What it adds to the run
Later nodes can read these, in a condition or as {{name}} in a text field.
| Value | Holds |
|---|---|
item | The item, on each path. |
Every path starts at onceThere's no limit on how many run at the same time yet, so a list of 500 calls to a URL makes 500 calls together.
Problems you might see
| Code | Means |
|---|---|
PARALLEL_FOREACH_WITHOUT_JOIN | The paths don't reach a Wait for paths. Shown when you publish. |
PFE_COLLECTION_NOT_ARRAY | The value at List isn't a list. |
PFE_FAN_OUT_TOO_LARGE | The list has more than 1,000 items. Nothing starts. |
Problems found when you publish stop the publish and point at the node. Problems while a run is going fail the node, and its On failure setting decides what happens next. See the error codes for the API's own.
See also
Waits for paths to arrive: all of them, the first one, or a number you set.
Outdefaultcontrol:joinRuns the body once per item of a list, one after another, then leaves by done.
Outbodydonecontrol:foreachSplits the run into named paths that carry on side by side.
Outone per path you namecontrol:fork