Skip to main content
The Pipeline gem allows you to run another pipeline from within your current pipeline. It supports conditional triggering, parameter passing, and metadata return for each run. Each Pipeline gem execution can trigger the target pipeline multiple times, with each instance running sequentially. The gem completes only after all triggered runs finish. This is useful for building orchestrated workflows directly in the visual canvas. You’ll find the gem under the Custom category in the gem drawer.
You can create pipelines solely dedicated to pipeline orchestration using multiple instances of this gem. Clearly label your orchestration pipelines to differentiate them from standard data pipelines.

​
Limitations

The Pipeline gem has the following limitations:
  • It can trigger only pipelines within the same project.
  • The Monitoring page doesn’t show the parent pipeline that triggered a run using the Pipeline gem.

​
Input and Output

The following table describes what the Pipeline gem expects as input and what it will produce as output.
PortDescription
in0Optional input dataset that may include a status column and additional columns.
Valid statuses include success, failure, or skipped.
Each row of the input triggers a separate pipeline run per Pipeline gem execution.
outOne output dataset that contains the metadata for each triggered pipeline run.
The Pipeline gem returns one row per triggered run.
When no input is connected:
  • The Pipeline gem triggers the child pipeline once.
  • The output contains a single row of metadata for that run.
When an input dataset is connected:
  • If a status column 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 status column 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.
ColumnTypeDescription
statusStringFinal status of the triggered pipeline: success, failure, or skipped.
pipelineRunIDStringUnique ID of the triggered pipeline run.
startTimeTimestampTime when the triggered pipeline started.
endTimeTimestampTime when the triggered pipeline finished.
errorStringError message, if any.
logsString ArrayLog messages from the triggered pipeline.
Pipelines are skipped when the input does not meet the trigger condition set in the gem.

​
Parameters

The Pipeline gem accepts the following parameters.
ParameterDescription
Pipeline to runSelect a pipeline to trigger in the list of pipelines from the same project.
Trigger only ifChoose a condition to control when the trigger fires based on the status column of the input dataset (if present). If the condition is not met, the Pipeline gem runs, but no pipelines are triggered. The output will show that all pipeline runs were skipped.
Maximum number of pipeline triggersSet a maximum number of times the child pipeline runs per Pipeline gem execution. Maximum is 10,000.
Set pipeline parametersSet values for the pipeline parameters defined in the child pipeline. You can specify constants, expressions, or column values for each parameter. If you don’t specify a value, the child pipeline uses its default parameter value.
Use multiple input rows to launch runs of the same pipeline with different sets of parameter values.

​
Trigger conditions

You can define the pipeline trigger condition by choosing from the following list.
  • Always run (default): Executes the pipeline unconditionally, regardless of input status (or absence of status).
  • All pipelines succeeded: Executes only when every input row has a success status.
  • All pipelines failed: Executes only when every input row has a failure status.
  • All pipelines finished: Executes after all input pipeline runs have completed, regardless of their success or failure.
  • Any pipeline succeeded: Executes if at least one input row has a success status.
  • Any pipeline failed: Executes if at least one input row has a failure status.

​
Execution behavior

Prophecy supports the following execution behaviors when running a Pipeline gem.
  • Sequential execution: When one Pipeline gem triggers a target pipeline multiple times, pipeline instances run sequentially. The Pipeline gem does not finish running until all instances of the target pipeline finish running.
  • Sequential triggering: Pipeline gems wait for upstream pipelines to finish running when multiple Pipeline gems are configured sequentially or are configured with sequential gem phases.
  • Parallel triggering: The gem supports parallel execution when separate pipeline branches have the same gem phase.
  • Recursive triggers: Recursive execution is supported. If a triggered pipeline contains another Pipeline gem, it will execute as expected.