¶ Description
Run a child pipeline in a loop.
¶ Parameters
¶ Parameters tab
Parameters:
-
Developer mode
Activate/deactivate the Code tab (advanced usage). -
Pipeline to run in the loop
Select the child pipeline that will be executed at each iteration. -
Global parameter name
Name of the GP that will be set for each iteration (default:gpname). -
Global parameter value
The value to assign to the GP on each iteration:- If an input table is connected, the
…button lets you select a column (one value per row). - If no input table is connected, you can provide a comma-separated list of values (inline mode).
- If an input table is connected, the
-
Global parameters to pass to the pipeline (separated by commas)
Optionalkey=valuelist to set/override additional GPs in the child pipeline. -
Clear the value of all global parameters before running the pipeline
Toggle ON to start each child execution from a clean GP state. -
Add an iteration counter
Adds a counter GP (values1..N) for each iteration. -
Iteration counter name
Default:gpcounter. Used only when the iteration counter option is ON. -
Number of pipelines to run in parallel
Concurrency level. Start with1, increase gradually. -
Silent mode
ON reduces console noise from children. -
Verbosity of messages in the log
Controls how much information you see for each executed child. -
On runtime error
Retry / abort strategy when a child execution fails.
¶ Description tab
See dedicated page for more information.
¶ Code tab
loopPipeline is a scripted action. Embedded code is accessible and customizable through this tab.
¶ Configuration tab
See dedicated page for more information.
¶ About
loopPipeline is a control action that executes the same child pipeline multiple times.
At each iteration, it sets one Global Parameter (defined by Global parameter name) to a different value, then runs the child pipeline once.
The number of iterations is driven by:
- the number of rows in the input table (column-driven mode), or
- the number of values in the inline list (inline mode).
If iterations are independent (no dependency between runs), you can increase Number of pipelines to run in parallel to speed up processing.
¶ Input
¶ Supported modes
-
Column-driven mode (recommended)
Connect a table to the input pin and set Global parameter value to a column.
The child pipeline runs once per row, using the column value as the GP value. -
Inline list mode
No input table required. Provide a comma-separated list in Global parameter value.
¶ Output
This action does not produce a transformed table by itself.
Its result is the side effects of the child pipeline executions (files in Records, database writes, etc.), and the execution details in the parent Log.
¶ Tips
- If running in parallel, make sure child outputs are unique per iteration (avoid overwriting the same filenames/paths).
- Use the iteration counter (e.g.
${gpcounter}) when you need unique output names.
¶ Troubleshooting
-
Child pipeline doesn’t receive the GP value
Ensure the child pipeline reads the GP (bind its parameter to the expected global parameter name). -
Outputs overwrite each other
Use unique naming (include the GP value and/or the iteration counter in output paths). -
Parallel runs fail intermittently
Lower parallelism or remove shared resources between iterations.
