Skip to content

Fix misleading log message in task_runner clear_on_success block - #67836

Merged
amoghrajesh merged 2 commits into
apache:mainfrom
astronomer:aip-103-backlog-misleadin-log
Jun 1, 2026
Merged

Fix misleading log message in task_runner clear_on_success block#67836
amoghrajesh merged 2 commits into
apache:mainfrom
astronomer:aip-103-backlog-misleadin-log

Conversation

@amoghrajesh

Copy link
Copy Markdown
Contributor

Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

Raised by @kaxil on PR #66859 post review comment.

The logs mention that "Task state will be cleared by the server because clear_on_success is enabled."

But _clear_backend_only() is called immediately after on the worker side, the backend
(e.g. custom S3 store) is cleared here, not by the server. Only the DB rows are cleared by
the server.


  • 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.

Comment threadtask-sdk/src/airflow/sdk/execution_time/task_runner.py Outdated
Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
@amoghrajesh
amoghrajesh merged commit 3090292 into apache:mainJun 1, 2026
115 checks passed
@amoghrajesh
amoghrajesh deleted the aip-103-backlog-misleadin-log branch June 1, 2026 12:54
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants

@amoghrajesh@kaxil