Loops

A Loop repeats a group of Workflow Steps for each item. For example, process an order's line items and create one row per item. Iterations run sequentially; a Loop is not a way to execute all items in parallel.

Add the Loop and its Steps

  1. Select an add-step control and choose Loop.
  2. In Loop configuration, select Loop over and configure its input.
  3. Set Maximum items and If an item fails.
  4. Use Preview items to inspect the resolved list, then select Continue to save.
  5. Add the Steps to repeat inside the Loop. Add work after End Loop when it should execute after iteration completes.

The current limit is 1–1,000 items per Loop. Exceeding the configured maximum fails validation; it does not silently process only the first part of the list. Up to five nested Loop levels are supported, so check how the item counts multiply before adding external Actions.

Choose an input mode

Loop overConfiguration
ArraySelect the complete array in Array. Each element becomes the current item.
Named listsUse Add named list, give each list a unique Field name, and select its array. Lists are paired by position and must have equal lengths.
TextProvide Text and a Delimiter. Named text fields can split several fields with the same delimiter and pair their values by position.
NumbersSet Start, End, and Increment. End is inclusive; a negative increment counts down. The increment must be nonzero and move toward End.

Named lists and named text support 1–32 uniquely named fields. Use letters, digits, and underscores, starting with a letter or underscore. The editor reports unavailable reserved names and invalid settings.

Trim whitespace around string items applies where string cleanup is appropriate. Under Advanced, Iteration number starts at changes the displayed iteration number only; the index still starts at zero and item order stays unchanged.

Map the current item

Inside the Loop, open an Action's Insert data picker and choose fields under Current loop item. For an array of order lines, map the current item's product and quantity rather than a fixed sample line from the Trigger.

Loop context also provides Index, Count, Iteration number, Is first, and Is last. Nested Loops can use their parent context. Select the correct level in the picker; a field from an unrelated branch or a future Step is not available.

Use Aggregate after a completed Loop when later work needs a summary of its results. Do not assume a child Action's single preview is a complete list of all iteration results. See Data mapping.

Preview items versus test execution

Preview items uses the current settings, including unsaved changes, and the selected test record. If no record is selected, it can use the latest available Trigger payload. It shows the data source, item count, and item table without executing Steps or calling connected apps. Nested previews use the first item from each parent Loop.

Test the Loop on the first item uses saved settings and runs the matching child Steps for that first item. Actions make real requests and can create, update, send, or delete data. Nested Loops test their first item under the first parent item. Delays and Destinations are simulated, and Steps after the Loop are not called.

Save changes before Test step. If the test fails, Retry test can resume using the same test requests and completed results. A new test or an individual Action test may repeat real effects. An empty input calls no child Steps.

Decide what happens on failure

In If an item fails, choose Stop the Loop or Skip remaining steps for that item and continue. Continuing allows later items to be attempted; it does not undo the failed item's earlier side effects or prove that every item succeeded.

A nonmatching Filter skips the rest of its route for that item. Other matching Paths can still execute, in order. Inspect per-item results rather than assuming a skipped route is a provider error.

Inspect and repair iterations

In Run history, expand the Loop's Loop iterations. Use Search iterations and Iteration status to find a failed item, then expand its child Step evidence. Open iteration link and Copy link identify a specific item, including nested iterations. Search coverage depends on the available recorded data and previews; missing evidence is not proof that an item never ran.

Where available, Retry failed iteration uses the latest saved Step settings, begins at the failed Step, and reuses successful results. Loop items and routes must remain unchanged. Other failed iterations and already completed work after the Loop are not repeated. Read Workflow retries before using it and check the provider for partial success.