GitHub user hnomichith added a comment to the discussion: Add the ability to backfill a DAG based on past Asset Events
Thanks for your answer. Given your answer, I'm not 100% sure we understood each other: the UX to "backfill" this DAG could be exactly the same as the one currently existing. It's just that currently, when you try to backfill a DAG triggered on Asset events, you select a time period, and it always shows "No runs matching selected criteria", independently of the events on which it would have reacted if it was already created and unpaused. The script (if you refer to it how I describe it) still has the caveat of running all downstream DAGs, and technically creating new events while conceptually the Asset has not been touched. It's a solution, but not really the most flexible IMO. If the POST `/api/v2/dags/:dag_id/assets/queuedEvents` was available, here indeed a script could do anything. What do you think? Was there a mis-understanding? GitHub link: https://github.com/apache/airflow/discussions/59886#discussioncomment-15373439 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
