[v3-1-test] Fix import errors not showing on UI (#61163)#61213
Merged
Conversation
ephraimbuddy
approved these changes
Jan 29, 2026
vincbeck
approved these changes
Jan 29, 2026
Import error stopped showing on UI after apache#60801 which removed the early bypass for users with access to all DAGs. When a DAG file has an import error, the DAG doesn't exist in DagModel (because it failed to import). The inner join with DagModel filters out these import errors because there's no matching row. This was always broken for users without "read all" permissions but was masked by the early return path.
79aa287 to
1262bf0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #61163
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.