pierrejeambrun opened a new pull request, #63360:
URL: https://github.com/apache/airflow/pull/63360
When a task group is renamed between DAG versions, the API's
get_task_instances endpoint was resolving task groups against the latest DAG
version instead of the version the run was created with. This caused 404 errors
when clicking on task groups in the grid view for historical runs.
The fix changes get_dag_for_run_or_latest_version to prefer the run's
created_dag_version_id, falling back to the existing behavior only when
unavailable.
To reproduce use this Dag:
- Start a run and wait for it to finish
- Flip the rename flag to true and reparse the Dag or wait a little bit for
v2 to come up
- Start a 2nd run
Then clicking on first run "process_data" task group will fail like the
screenshot below
```
from __future__ import annotations
from datetime import datetime
from airflow.providers.standard.operators.empty import EmptyOperator
from airflow.sdk import DAG, TaskGroup
RENAME = False # flip to True after step 2
group_id = "process_data_v2" if RENAME else "process_data"
with DAG(
dag_id="repro_task_group_not_found",
start_date=datetime(2024, 1, 1),
schedule=None,
):
with TaskGroup(group_id=group_id) as tg:
EmptyOperator(task_id="step_1")
EmptyOperator(task_id="step_2")
EmptyOperator(task_id="done") << tg
```
### Before
<img width="1920" height="806" alt="Screenshot 2026-03-11 at 17 54 49"
src="https://github.com/user-attachments/assets/569cad5c-ca75-4e2f-b537-46c09678a4b9";
/>
### After
<img width="1917" height="943" alt="Screenshot 2026-03-11 at 17 53 27"
src="https://github.com/user-attachments/assets/789f814f-172a-424e-b485-2011b928be76";
/>
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [ ] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
