Overview
Triggers for a pipeline.
Pipeline schedule object
Date and time the trigger was created.
Event matching logic for event triggers.
Trigger ID.
Name of trigger.
Pipeline UUID the trigger belongs to.
@once, @hourly, @daily, @weekly, @monthly
Trigger type: api, event, time
Additional settings for the trigger.
If true, then blocks in the pipeline will continue to run even if unrelated blocks fail.
If true, then an initial pipeline run will be created immediately after enabling the
trigger if the trigger’s current execution date is after its start date time but before
current time.
For example, if the current time is 1/4/24 12:00 UTC and you create a daily trigger, the
current execution date would be 2024-01-04 00:00. If the start date was set to
1/3/24 12:00 UTC, which is before the current execution date, and the create_initial_pipeline_run
setting was enabled, a pipeline run with execution date 2024-01-04 00:00 would get created
immediately.
If true, then new pipeline runs won’t be triggered until the most recent pipeline run is
no longer running.
If the pipeline run has been running for more than the SLA value, then the pipeline will fail.
Date and time when the trigger should start running.
active, inactive
An array of tag names.
Unique string used in the URL when triggering pipeline via API request.
Date and time the trigger was last updated.
Object containing variables for the pipeline that is being overwritten by this trigger.
The property name is user defined.
Was this page helpful?