Hevo Trigger
The HevoTrigger is used by deferrable operators and sensors for async monitoring. A trigger is automatically created when the operator or sensor uses deferrable=True.
Parameters
The HevoTrigger accepts the following parameters:
| Name | Type | Default | Description |
|---|---|---|---|
pipeline_id (Required) |
INT |
NA | The unique identifier of the Hevo Pipeline to be monitored. |
job_id |
STR |
None | The ID of the job to be monitored. If a job ID is not specified, the trigger identifies the active job via auto-discovery. |
job_typeNote: This parameter is used when a job_id is not specified. |
- JobType- STR
|
INCREMENTAL | The type of job to be monitored when a job ID is not specified. The trigger discovers the relevant job based on the specified type. Allowable values: INCREMENTAL: A job that syncs new and updated data. HISTORICAL: A job that syncs all existing data from the Source. RESYNC: A job that re-ingests historical data for all active objects in the Pipeline and updates the Destination tables if changes are detected in the re-ingested data. RESYNC_WITH_DROP_AND_LOAD: A job that drops and recreates the Destination tables for all active objects in the Pipeline. During this process, the tables are temporarily unavailable. Hevo then re-ingests all data from the Source objects and loads it into the newly created Destination tables. |
poke_interval |
INT |
15 | The time (in seconds) between the asynchronous status checks while waiting for the Pipeline job to complete. |
accept_completed_with_failures |
BOOL |
False | A flag to treat the Pipeline job’s Completed with Failures status as success. |
connection_id |
STR |
hevo_airflow_conn_id | The ID of the connection created in Airflow for Hevo API credentials and connection details. |
The following table lists the methods that the HevoTrigger provides:
| Method | Description |
|---|---|
serialize |
Converts the trigger parameters into a format, such as JSON, that can be saved to Airflow’s metadata database, allowing the process to be resumed even after an Airflow restart. |
run |
Executes the monitoring logic until the Pipeline job reaches the final state, and sends a TriggerEvent back to the process that called the trigger. |
Last updated on Mar 02, 2026