GitHub user TinoSM added a comment to the discussion: Duplicate dag ids lead to confusing outcome rather than error.
As an idea, maybe it would be nice to have a warning (similar to existing errors which show in Airflow UI) if there's ping-pong in DAG executions? I.e. if I execute a DAG and it was created from file X (define file as any source "id", database, file...). Then in the window of 2 minutes it runs from a different source with the same DAG-name. Then in the window of 2 minutes runs again... It would only need a local cache keeping the DAGs which were started during the window. Not a 100% ensured mechanism (to keep the cache "local"), but end of the day it would help people debug this issue (which is hard to debug even when you are the one who messed it up). GitHub link: https://github.com/apache/airflow/discussions/24709#discussioncomment-13639492 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
