Skip to content

Loop Iterator

The Loop Iterator component lets users loop over values of a simple sequence.

This component is a simple for loop. It enables you to run an attached component multiple times, each time with a unique value of an iteration variable. That variable can be referenced from the attached component.

To attach the iterator to another component, use the connection ring beneath the file iterator to connect to the input of the other component. The two components will automatically "snap" together, with the file iterator sitting on top of the other component, and can be dragged around the canvas as a single component. To uncouple the two components, delete the loop iterator component.

If you need to iterate more than one component, put them into a separate orchestration pipeline or transformation pipeline and use a Run Transformation or Run Orchestration component attached to the iterator. In this way, you can run an entire pipeline flow 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.

Concurrency = drop-down

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

Full SaaS deployments are limited to 20 concurrent tasks, with additional tasks being queued. Hybrid SaaS deployments with customer-hosted agents have 20 concurrent tasks per agent instance, with a maximum of 100 instances if configured accordingly.

Variable to Iterate = drop-down

Choose an existing variable to iterate. Only numeric variable types are available.

Starting Value = integer

The starting value for the variable. Starting and ending values are both inclusive.

Increment Value = integer

The increment value for the variable. This may be negative, providing the end value is smaller than the starting value.

End Value = integer

The end value for the variable. Starting and ending values are both inclusive.

Break on Failure = drop-down

  • 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 does not run successfully, fail immediately.

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

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

Snowflake Databricks Amazon Redshift (preview)