GitHub user dylannz edited a comment on the discussion: Why is
AIRFLOW__CELERY__TASK_ACKS_LATE True by default?
I had this problem on Airflow 3.1.7 as well, and it manifested in the logs as:
```
[2026-03-10 08:55:46] ERROR - Server indicated the task shouldn't be running
anymore. Terminating process
detail={"detail":{"reason":"not_running","message":"TI is no longer in the
running state and task should terminate","current_state":"failed"}}
[2026-03-10 08:55:51] ERROR - Task killed!
```
Took me a very long time to debug it, but setting
`AIRFLOW__CELERY__TASK_ACKS_LATE=False` fixed it. Leaving this comment here so
that anyone searching for the above error will hopefully find this issue...
I am using Redis as a broker, which I believe is an important detail in this
instance as well. By default, anyone using this setup will not be able to run
jobs longer than 1 hour (as the default visibility_timeout is 3600).
GitHub link:
https://github.com/apache/airflow/discussions/57348#discussioncomment-16058947
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
