Skip to content

Grid Iterator

The Grid Iterator component implements a loop over the rows of a grid variable. This runs an attached component multiple times, each time using a different row of values from the grid.

To attach the iterator to another component, add the required component to the canvas then click the blue output connector on the Grid Iterator and drag a link to the component.

If you need to iterate more than one component, put them into a separate orchestration or transformation pipeline and run this pipeline through a Run Transformation or Run Orchestration component attached to the iterator. In this way, you can run an entire pipeline multiple times, once for each row of variable values.

All iterator components are limited to a maximum 5000 iterations.


Name = string

A human-readable name for the component.

Grid Variable = drop-down

Choose an existing grid variable to iterate.

Grid Iterator Variable Mapping = columns editor

  • Grid Column Name: Enter the grid column name.
  • Variable Name: Choose an existing variable.

Break On Failure = boolean

If a failure occurs during any iteration, the failure link is followed. This parameter controls whether it's followed immediately or after all iterations have been attempted.

  • No: Attempt to run the attached component for each iteration, regardless of success or failure. This is the default setting.
  • Yes: If the attached component doesn't run successfully, fail immediately.

This property is only available when Concurrency is set to Sequential. When set to Concurrent, all iterations will be attempted.

Concurrency = drop-down

  • Concurrent: Iterations run concurrently.
  • Sequential: Iterations run in sequence, waiting for each to complete before starting the next. This is the default setting.

In Sequential mode, the iterations will always proceed in the same order that the data is held in the grid variable. So the first iteration will use values from the first row of the grid, the second will use the second row of the grid, and so on.

The maximum concurrency is limited by the number of available threads (2x the number of processors on the cloud instance).

Snowflake Databricks Amazon Redshift (preview)