Overview
Programmatically create multiple pipeline runs to backfill a pipeline.
Backfill object
If the backfill uses custom code to generate the pipeline runs, this block UUID contains the code that will be used.
Date and time the backfill finished running successfully.
Date and time the record was created.
The date and time the backfill should stop on.
Date and time the backfill failed.
Unique ID for the record.
minute
, hour
, day
, week
, month
, year
The number of interval_type
to use in between each pipeline run that the backfill creates.
For example, if interval_type
is day
and interval_units
is 3, then the backfill will create
pipeline runs spanning 3 day increments between the start_datetime
and end_datetime
.
Various metrics related to the pipeline run; e.g. number of rows processed in a data integration pipeline sync.
Name of the record.
Pipeline schedule that this record belongs to.
Pipeline that this record belongs to.
The date and time the backfill should start on.
Date and time the backfill started running.
initial
, running
, completed
, failed
, cancelled
Number of pipeline runs that will be created for this backfill.
Date and time the record was last updated.
Object containing variables for the pipeline that is being overwritten by this backfill.
Was this page helpful?