Set task name for 2.11.X path by o-nikolas · Pull Request #63746 · apache/airflow

o-nikolas · 2026-03-16T19:14:28Z

Celery now uses explicit task names when submitting tasks to workers (see send_workload_to_executor), make sure to set that explicit name on the older module level app that Airflow 2.x uses.

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

Yes (please specify the tool below)
claude

Read the 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) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:16:14Z

CC @potiuk @Aakcht @kalluripradeep

o-nikolas · 2026-03-16T19:59:18Z

CI image builds are broken in main

kalluripradeep · 2026-03-16T20:57:56Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.

You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.

The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

o-nikolas · 2026-03-16T21:27:50Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.
You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.
The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

Thanks for the review @kalluripradeep! If it looks good to you, please approve the PR 🙂

Also any testing is always welcomed, especially with this type of edge case. I tests manually but please double check my work

Aakcht

Hi, tested it, the fix seems to help, thanks!

potiuk · 2026-03-17T00:20:28Z

Hi, tested it, the fix seems to help, thanks!

Cooool Thanks !

potiuk · 2026-03-17T00:26:56Z

Failure unrelated - fixing it in #63763

potiuk · 2026-03-17T00:57:33Z

Needs rebase I think

o-nikolas · 2026-03-18T22:40:28Z

Needs rebase I think

After pulling in main the tests are green. Merging!

potiuk · 2026-03-21T16:18:55Z

cool

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:14:28Z

fixes#63729

Celery now uses explicit task names when submitting tasks to workers (see send_workload_to_executor), make sure to set that explicit name on the older module level app that Airflow 2.x uses.

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

Yes (please specify the tool below)
claude

Read the 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) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:16:14Z

CC @potiuk @Aakcht @kalluripradeep

o-nikolas · 2026-03-16T19:59:18Z

CI image builds are broken in main

kalluripradeep · 2026-03-16T20:57:56Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.

You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.

The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

o-nikolas · 2026-03-16T21:27:50Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.
You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.
The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

Thanks for the review @kalluripradeep! If it looks good to you, please approve the PR 🙂

Also any testing is always welcomed, especially with this type of edge case. I tests manually but please double check my work

Aakcht

Hi, tested it, the fix seems to help, thanks!

potiuk · 2026-03-17T00:20:28Z

Hi, tested it, the fix seems to help, thanks!

Cooool Thanks !

potiuk · 2026-03-17T00:26:56Z

Failure unrelated - fixing it in #63763

potiuk · 2026-03-17T00:57:33Z

Needs rebase I think

o-nikolas · 2026-03-18T22:40:28Z

Needs rebase I think

After pulling in main the tests are green. Merging!

potiuk · 2026-03-21T16:18:55Z

cool

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:14:28Z

fixes#63729

Celery now uses explicit task names when submitting tasks to workers (see send_workload_to_executor), make sure to set that explicit name on the older module level app that Airflow 2.x uses.

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

Yes (please specify the tool below)
claude

Read the 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) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:16:14Z

CC @potiuk @Aakcht @kalluripradeep

o-nikolas · 2026-03-16T19:59:18Z

CI image builds are broken in main

kalluripradeep · 2026-03-16T20:57:56Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.

You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.

The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

o-nikolas · 2026-03-16T21:27:50Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.
You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.
The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

Thanks for the review @kalluripradeep! If it looks good to you, please approve the PR 🙂

Also any testing is always welcomed, especially with this type of edge case. I tests manually but please double check my work

Aakcht

Hi, tested it, the fix seems to help, thanks!

potiuk · 2026-03-17T00:20:28Z

Hi, tested it, the fix seems to help, thanks!

Cooool Thanks !

potiuk · 2026-03-17T00:26:56Z

Failure unrelated - fixing it in #63763

potiuk · 2026-03-17T00:57:33Z

Needs rebase I think

o-nikolas · 2026-03-18T22:40:28Z

Needs rebase I think

After pulling in main the tests are green. Merging!

potiuk · 2026-03-21T16:18:55Z

cool

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:14:28Z

fixes#63729

Celery now uses explicit task names when submitting tasks to workers (see send_workload_to_executor), make sure to set that explicit name on the older module level app that Airflow 2.x uses.

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

Yes (please specify the tool below)
claude

Read the 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) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:16:14Z

CC @potiuk @Aakcht @kalluripradeep

o-nikolas · 2026-03-16T19:59:18Z

CI image builds are broken in main

kalluripradeep · 2026-03-16T20:57:56Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.

You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.

The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

o-nikolas · 2026-03-16T21:27:50Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.
You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.
The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

Thanks for the review @kalluripradeep! If it looks good to you, please approve the PR 🙂

Also any testing is always welcomed, especially with this type of edge case. I tests manually but please double check my work

Aakcht

Hi, tested it, the fix seems to help, thanks!

potiuk · 2026-03-17T00:20:28Z

Hi, tested it, the fix seems to help, thanks!

Cooool Thanks !

potiuk · 2026-03-17T00:26:56Z

Failure unrelated - fixing it in #63763

potiuk · 2026-03-17T00:57:33Z

Needs rebase I think

o-nikolas · 2026-03-18T22:40:28Z

Needs rebase I think

After pulling in main the tests are green. Merging!

potiuk · 2026-03-21T16:18:55Z

cool

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:14:28Z

fixes#63729

Celery now uses explicit task names when submitting tasks to workers (see send_workload_to_executor), make sure to set that explicit name on the older module level app that Airflow 2.x uses.

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

Yes (please specify the tool below)
claude

Read the 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) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:16:14Z

CC @potiuk @Aakcht @kalluripradeep

o-nikolas · 2026-03-16T19:59:18Z

CI image builds are broken in main

kalluripradeep · 2026-03-16T20:57:56Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.

You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.

The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

o-nikolas · 2026-03-16T21:27:50Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.
You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.
The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

Thanks for the review @kalluripradeep! If it looks good to you, please approve the PR 🙂

Also any testing is always welcomed, especially with this type of edge case. I tests manually but please double check my work

Aakcht

Hi, tested it, the fix seems to help, thanks!

potiuk · 2026-03-17T00:20:28Z

Hi, tested it, the fix seems to help, thanks!

Cooool Thanks !

potiuk · 2026-03-17T00:26:56Z

Failure unrelated - fixing it in #63763

potiuk · 2026-03-17T00:57:33Z

Needs rebase I think

o-nikolas · 2026-03-18T22:40:28Z

Needs rebase I think

After pulling in main the tests are green. Merging!

potiuk · 2026-03-21T16:18:55Z

cool

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:14:28Z

fixes#63729

Celery now uses explicit task names when submitting tasks to workers (see send_workload_to_executor), make sure to set that explicit name on the older module level app that Airflow 2.x uses.

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

Yes (please specify the tool below)
claude

Read the 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) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:16:14Z

CC @potiuk @Aakcht @kalluripradeep

o-nikolas · 2026-03-16T19:59:18Z

CI image builds are broken in main

kalluripradeep · 2026-03-16T20:57:56Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.

You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.

The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

o-nikolas · 2026-03-16T21:27:50Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.
You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.
The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

Thanks for the review @kalluripradeep! If it looks good to you, please approve the PR 🙂

Also any testing is always welcomed, especially with this type of edge case. I tests manually but please double check my work

Aakcht

Hi, tested it, the fix seems to help, thanks!

potiuk · 2026-03-17T00:20:28Z

Hi, tested it, the fix seems to help, thanks!

Cooool Thanks !

potiuk · 2026-03-17T00:26:56Z

Failure unrelated - fixing it in #63763

potiuk · 2026-03-17T00:57:33Z

Needs rebase I think

o-nikolas · 2026-03-18T22:40:28Z

Needs rebase I think

After pulling in main the tests are green. Merging!

potiuk · 2026-03-21T16:18:55Z

cool

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:14:28Z

fixes#63729

Celery now uses explicit task names when submitting tasks to workers (see send_workload_to_executor), make sure to set that explicit name on the older module level app that Airflow 2.x uses.

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

Yes (please specify the tool below)
claude

Read the 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) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:16:14Z

CC @potiuk @Aakcht @kalluripradeep

o-nikolas · 2026-03-16T19:59:18Z

CI image builds are broken in main

kalluripradeep · 2026-03-16T20:57:56Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.

You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.

The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

o-nikolas · 2026-03-16T21:27:50Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.
You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.
The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

Thanks for the review @kalluripradeep! If it looks good to you, please approve the PR 🙂

Also any testing is always welcomed, especially with this type of edge case. I tests manually but please double check my work

Aakcht

Hi, tested it, the fix seems to help, thanks!

potiuk · 2026-03-17T00:20:28Z

Hi, tested it, the fix seems to help, thanks!

Cooool Thanks !

potiuk · 2026-03-17T00:26:56Z

Failure unrelated - fixing it in #63763

potiuk · 2026-03-17T00:57:33Z

Needs rebase I think

o-nikolas · 2026-03-18T22:40:28Z

Needs rebase I think

After pulling in main the tests are green. Merging!

potiuk · 2026-03-21T16:18:55Z

cool

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:14:28Z

fixes#63729

Celery now uses explicit task names when submitting tasks to workers (see send_workload_to_executor), make sure to set that explicit name on the older module level app that Airflow 2.x uses.

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

Yes (please specify the tool below)
claude

Read the 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) is needed.
When adding dependency, check compliance with the ASF 3rd Party License Policy.
For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas · 2026-03-16T19:16:14Z

CC @potiuk @Aakcht @kalluripradeep

o-nikolas · 2026-03-16T19:59:18Z

CI image builds are broken in main

kalluripradeep · 2026-03-16T20:57:56Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.

You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.

The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

o-nikolas · 2026-03-16T21:27:50Z

Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746.
You're right — my fix in #63110 correctly registered execute_workload for the Airflow 3.x path but missed that the Airflow 2.x execute_command task name needed to be set explicitly to match what workers expect.
The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed.

Thanks for the review @kalluripradeep! If it looks good to you, please approve the PR 🙂

Also any testing is always welcomed, especially with this type of edge case. I tests manually but please double check my work

Aakcht

Hi, tested it, the fix seems to help, thanks!

potiuk · 2026-03-17T00:20:28Z

Hi, tested it, the fix seems to help, thanks!

Cooool Thanks !

potiuk · 2026-03-17T00:26:56Z

Failure unrelated - fixing it in #63763

potiuk · 2026-03-17T00:57:33Z

Needs rebase I think

o-nikolas · 2026-03-18T22:40:28Z

Needs rebase I think

After pulling in main the tests are green. Merging!

potiuk · 2026-03-21T16:18:55Z

cool

fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

Set task name for 2.11.X path
a44a546
fixesapache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.

o-nikolas requested review from dheerajturaga and hussein-awala as code owners March 16, 2026 19:14

o-nikolas added the full tests needed We need to run full set of tests for this PR to merge label Mar 16, 2026

boring-cyborgBot added area:providers provider:celery labels Mar 16, 2026

o-nikolas requested a review from potiuk March 16, 2026 19:15

o-nikolas mentioned this pull request Mar 16, 2026
Celery provider 3.17.1 breaks Airflow 2.11.2 #63729
Closed
2 tasks

eladkal approved these changes Mar 16, 2026
View reviewed changes

kalluripradeep approved these changes Mar 16, 2026
View reviewed changes

Aakcht approved these changes Mar 16, 2026
View reviewed changes

Merge branch 'main' into onikolas/fix_celery_task_key
2cf5cd2

potiuk approved these changes Mar 17, 2026
View reviewed changes

Merge branch 'main' into onikolas/fix_celery_task_key
631bfd9

o-nikolas merged commit 2d2d8a2 into apache:mainMar 18, 2026
134 checks passed

o-nikolas deleted the onikolas/fix_celery_task_key branch March 18, 2026 22:40

jscheffl mentioned this pull request Mar 24, 2026
Status of testing Providers that were prepared on March 24, 2026 #64195
Closed