Pipeline Chains

Pipeline chains automatically create tasks in a target pipeline when tasks complete in a source pipeline. This is useful for building multi-stage processes where each stage is a separate pipeline.

Trigger types

On task completion

A new task is created in the target pipeline each time a task completes in the source pipeline. Every completed source task produces one target task.

Example: A labeling pipeline feeds into a review pipeline, where each labeled item gets a separate quality review.

On pipeline completion

Tasks are created in the target pipeline only after all tasks in the source pipeline have reached Finished status. Tasks in Failed, Escalated, or Quarantined status will block this trigger — they must be resolved first.

Example: A data collection pipeline finishes, then an analysis pipeline runs over the complete dataset.

Creating a chain

1. Open the target pipeline's Data Explorer and click Create Tasks.
2. Select the Chaining tab.
3. Choose a source pipeline from the dropdown. The source can be from the same project or a different project within your organization.
4. Select a trigger type — On Task Completion or On Pipeline Completion.
5. The platform auto-matches fields by name. Use the field mapping editor to review matches, manually map unmatched fields, or skip fields. For JSON-typed source fields, you can extract specific paths from the JSON structure.
6. Click Run Chain.

Mapped fields are seeded as dataset (predefined) values in the target tasks. Unmapped fields will be empty and can be filled by contributors or generated by LLMs.

Managing chains

Existing chains are listed in the Chaining tab. You can edit a chain's trigger type and field mappings, or delete it.

Constraints

• Chains cannot create circular dependencies (A → B → A).
• A pipeline can chain to multiple targets, but only one chain is allowed per source, target, and trigger type combination.
• Field mappings do not update automatically when pipeline fields change — update mappings after publishing a new pipeline version.
• The target pipeline must be Active or Paused to receive chained tasks.