Input and Output
The following table describes what the Pipeline gem expects as input and what it will produce as output.
When no input is connected:
- The Pipeline gem triggers the child pipeline once.
- The output contains a single row of metadata for that run.
- If a
statuscolumn is present, it is used to evaluate trigger conditions. If the trigger condition is met, the Pipeline gem triggers the child pipeline once for each input row. - If a
statuscolumn is not present, the Pipeline gem always triggers the child pipeline once for each input row. - Additional columns can be used to pass parameter values into each run.
- The output contains one row of metadata per input row.
The input dataset can be any dataset (including the output of an upstream Pipeline gem).
Output schema
Each row in the output table represents a pipeline run triggered from the Pipeline gem. The output schema provides you with the following information for each pipeline run.Pipelines are
skipped when the input does not meet the trigger condition set in the gem.Parameters
The Pipeline gem accepts the following parameters.Version
By default, the Pipeline gem triggers whatever version of the target pipeline is currently in the working tree. You can choose to lock it to a specific published version using the Last Released option.Changing Pipeline to run resets Version back to Current.
When you run a pipeline from a dependency project, the gem always runs the version of that project that your project depends on. You can’t select a different version.
Only published versions that include the target pipeline are selectable. Versions that don’t include it appear disabled in the list.
Trigger conditions
A Pipeline gem requires at least one non-empty input row to execute. If input is empty, the pipeline will not run, even when trigger condition is set to Always run.
The trigger conditions treat any
status value other than success as a failure.
Iterator mode
Use iterator mode to run the same child pipeline repeatedly, for example to process data in rounds until nothing is left to process. Iterator mode applies only when the Pipeline gem has no input connected. When you enable Iterator mode, the Pipeline gem runs the child pipeline one iteration at a time, up to Maximum number of pipeline triggers. If you don’t set a maximum, the limit is 10,000 iterations. You can also configure the following optional fields.
The output of the Pipeline gem contains one row for each iteration.

