DAG Import Errors remain in the WebUI even after fix error

[sanromeo]

Apache Airflow version

2.9.1

If "Other Airflow 2 version" selected, which one?

2.9.0, 2.9.1

What happened?

DAG Import Errors remain in the WebUI even after fix error

What you think should happen instead?

DAG Import Errors will disappear in WebUI after fix errors

How to reproduce

1. Create DAG with broken parameters that will cause DAG Import Errors.
2. Look at Airflow WebUI, you will see error.
3. Fix it :)
4. Error will remain the same in WebUI but should disappear after fix.

Operating System

MacOS or Linux

Versions of Apache Airflow Providers

Deployment

Official Apache Airflow Helm Chart

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

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[eladkal]

I can't reproduce this.
Please provide reproduce example

[sanromeo]

Sorry, it's not related to all errors, only to ValidationError with pydantic for me
airflow dags list-import-errors -o json show no errors
but in Web UI there is still error appear
Also link to reddit thread:
https://www.reddit.com/r/apache_airflow/comments/14oji77/airflow_262_and_pydantic_warningserrors/

Seems it happenned after upgrate pydantic to 2.+ version

[KulykDmytro]

Data remains in import_errors table despite of fixed DAG code
Started to appear since 2.9.0 upgrade

[Taragolis]

Check on both 2.9.0 and 2.9.1 by use sample docker compose

With this DAG it worked as expected

from __future__ import annotations

from datetime import datetime, timezone

from airflow.decorators import task
from airflow.models.dag import DAG

raise RuntimeError("Boooom!")

START_DATE = datetime(2024, 2, 29, tzinfo=timezone.utc)


with DAG("issue_39762", schedule="@once", tags=["issue", "39762", "dag-import"], start_date=START_DATE):
    @task
    def do_nothing(): ...

    do_nothing()

Gone from both DB and UI as soon as I comment out / remove raise RuntimeError("Boooom!")

---

Expected to see some examples and more information about your configurations

[sanromeo]

The root cause was that we have our own DagFactory and did not use the processor_subdir parameter in errors.ImportError since we have one DAG-processor, so we specified the folder with dags as processor_subdir and the problem was solved.