sunank200 commented on issue #49618: URL: https://github.com/apache/airflow/issues/49618#issuecomment-2827729287
I checked this behaviour in version 2.10.5, and it is the same as in 3.0. If a DAG has been executed in previous runs but encounters an import error now, it will still appear on the Airflow DAGS list UI, along with the relevant import errors displayed on the main DAG list page. However, if a DAG has never been run and has import errors, it will not be shown in the DAGs list at all. In contrast, if the DAG has been executed in the past and now faces import errors, it will still be listed, but will show the import errors only in the designated import error section in Airflow 3.0. I believe we should keep the past run DAGs in the list even though they have import errors, as this reflects the user's previous run history. WDYT? If we want to change this behaviour, it would be a different behaviour than the past in terms of DAGS listing. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
