venkatamandavilli-code commented on issue #45227: URL: https://github.com/apache/airflow/issues/45227#issuecomment-4724960872
Thanks for reporting this. This seems like an important usability issue because DAG import errors are often used by operators to identify active problems in the DAG repository. If the error remains visible after the broken DAG has been removed, users may continue investigating a problem that no longer exists. From an operations perspective, stale import errors can create confusion during deployment validation, GitSync-based DAG updates, and production support activities. It would be helpful if Airflow could either automatically clear import errors when the corresponding DAG file no longer exists, or provide clearer information about where the import error is persisted and how it can be resolved. The GitSync scenario described here is especially relevant because DAG files can be added, updated, and removed frequently. In that case, the UI should ideally reflect the current DAG repository state and not keep showing errors for deleted DAG files. I would be interested in helping investigate this further if maintainers think this is suitable for a first contribution. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
