Repository navigation
Nested task group names are not generated properly #41596
Description
Apache Airflow version
2.9.3
If "Other Airflow 2 version" selected, which one?
No response
What happened?
When the same task group gets called multiple times within a task group, a airflow.exceptions.DuplicateTaskIdFound is raised. See print_k_group_inner in the following example. Note that if you comment out one of the print_k_group_inner, the top-level task groups are named correctly to print_k_group and print_k_group__1.
What you think should happen instead?
There should be 4 task groups created and no errors raised.
-print_k_group.print_k_group_inner
-print_k_group.print_k_group_inner__1
-print_k_group__1.print_k_group_inner
-print_k_group__1.print_k_group_inner__1
How to reproduce
from airflow.decorators import dag, task_group, task
from pendulum import datetime
@dag(
start_date=datetime(2023, 7, 1),
schedule=None,
catchup=False,
tags=["@task_group", "dependencies"],
)
def test_tg():
@task
def get_k():
return 10
@task
def print_k(k):
print(k)
@task_group
def print_k_group(k):
print_k_group_inner(k)
print_k_group_inner(k)
@task_group
def print_k_group_inner(k):
print_k(k)
k = get_k()
print_k_group(k)
print_k_group(k)
test_tg()
Operating System
Ubuntu 22.04.4 LTS
Versions of Apache Airflow Providers
None
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
Activity
boring-cyborg commentedon Aug 19, 2024
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.
isaiahiruoha commentedon Jul 25, 2025
Update 2025, reproduced in version 2.11.0, fixed in version 3.0.0
eladkal commentedon Jul 27, 2025
So you were unable to reproduce on 3.x?
isaiahiruoha commentedon Jul 27, 2025
Correct, on version 3.x the same DAG functions correctly with the expected nested naming instead of throwing DuplicateTaskIdFound.
eladkal commentedon Jul 27, 2025
Closing as fixed