Repository navigation
Trigger and Watcher it not running for External-Event Driven Dag #64617
Description
Apache Airflow version
latest v3-2-test branch and cherry-picked both #64598 patch and #64615 patch
Reproduce Step
Either a. or b. can work
a.
minimum Dag by @uranusjr
from __future__ import annotations
from airflow.providers.apache.kafka.triggers.await_message import AwaitMessageTrigger
from airflow.sdk import DAG, Asset, AssetWatcher, task
trigger = AwaitMessageTrigger(topics=())
asset = Asset("x", watchers=[AssetWatcher("am", trigger)])
with DAG(dag_id="t", schedule=asset) as dag:
passb.
follow #64613 to reproduce with e2e flow
What happened
The Triggerer showing no trigger and watcher is running:
Additiaonlly, it show 0 tigger in the DB:
airflow=# SELECT * FROM trigger;
id | classpath | kwargs | created_date | triggerer_id | queue
----+-----------+--------+--------------+--------------+-------
(0 rows)
What you think should happen instead?
No response
Operating System
Breeze
Versions of Apache Airflow Providers
No response
Deployment
None
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Activity
jason810496 commentedon Apr 2, 2026
Entrypoint of the
add_asset_trigger_referencesinairflow-core/src/airflow/dag_processing/collection.pyMy plan: verifying the serialization result from the
v3-1-testand thev3-2-test(including #64598 patch and #64615 patch)I found that running
airflow dags reserializeexplicitly in another shell make the trigger show up in DB -> then make the triggers start running.Perhaps we can check the dag-parsing different starting from the
airflow dags reserializeCLI and Dag-processor paring entrypoint.Noted that: We can only show trigger RIGHT AFTER running the
airflow dags reserialize, when the new dag-parsing loop comes, the triggers will be deleted from DB again.Behavior by timeline:
airflow dags list-> double checked the Dag is inunpausestate via Airflow UIPGPASSWORD='airflow' psql -h postgres -U postgres -d airflow -c "SELECT * FROM trigger;"-> showing 0 rowsairflow dags reserializePGPASSWORD='airflow' psql -h postgres -U postgres -d airflow -c "SELECT * FROM trigger;", showing trigger nowPGPASSWORD='airflow' psql -h postgres -U postgres -d airflow -c "SELECT * FROM trigger;"-> showing 0 rows due to new dag-parsing loop