Add missing dag_id filter on DagRun query

[jvstein]

We are upgrading an Airflow 2.11.0 system to 3.1.7 and encountered a problem where clicking a Task Group in the grid UI was giving a 404 response in the Task Instance detail pane.

I traced it back to a missing dag_id filter when building the list of task instances. The initial query on dag_run happens without a dag_id filter, which is very likely to return a different DAG sharing a similar schedule (e.g. run_id scheduled__2026-02-03T04:00:00+00:00). That DagRun is then subsequently used for later filtering and the relevant downstream logic can't find the task group being used for filtering.

This change adds the dag_id filter when querying and rejects inputs that don't include a valid dag_id to filter when dag_run_id is specified.

• closes: [Bug][Airflow 3 API] TaskGroup UI 404 Not Found due to missing dag_id filter when querying identical run_ids #62684

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Generated-by: Claude Code (Opus 4.5 model)

[pierrejeambrun]

Nice looking good overall, just one adjustment needed.

[waltervillarreal]

Thank you very much for the quick fix! I'm impressed by how fast this issue was addressed and how quickly the PR was created.

(Apologies if this isn't the standard place for thanks—I'm still getting familiar with the workflow, so please let me know if I should use a different channel next time).

Thanks again for the amazing work!

[jvstein]

Thank you very much for the quick fix! I'm impressed by how fast this issue was addressed and how quickly the PR was created.

I just happened to be running into the same problem around the same time as you. Great job documenting the problem on your issue! I had forgotten to look for open issues before just diving into a PR, but yours was very easy to find and confirm all the details on.

[Enzzo657]

@jvstein Hello, please tell me in which version this problem is fixed. Just yesterday we updated to 3.1.7 from 3.0.0, and some tasks were completed successfully, but this error is still present and the logs cannot be viewed.

[jvstein]

@jvstein Hello, please tell me in which version this problem is fixed. Just yesterday we updated to 3.1.7 from 3.0.0, and some tasks were completed successfully, but this error is still present and the logs cannot be viewed.

If you click on the merged commit to main (ec75118) from the GitHub log and look at the tags at the top it will show you the version of the release. Backports sometimes have a different commit, but that doesn't apply here.

In this case, the fix was first included in 3.2.0.