dagProcessor liveness probe always fails

[IanSweeneyKodiak]

Under which category would you file this issue?

Helm chart

Apache Airflow version

3.2.2 (helm 1.2.2)

What happened and how to reproduce it?

Default helm chart uses livenessProbe with command: ~ for dagProcessor.
This uses the default command to check liveness which always fails:
airflow jobs check --job-type DagProcessorJob --hostname $(hostname)
Causing the dagProcessor to be restarted by k8s every 5min (livenessProbe failure)

What you think should happen instead?

No response

Operating System

No response

Deployment

Official Apache Airflow Helm Chart

Apache Airflow Provider(s)

No response

Versions of Apache Airflow Providers

No response

Official Helm Chart version

1.22.0 (latest released)

Kubernetes Version

No response

Helm Chart configuration

No response

Docker Image customizations

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

[boring-cyborg]

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.

[IanSweeneyKodiak]

Turns out there is a running dagProcessor job in the db but the cli used for the health check returns no alive jobs
select * from job where job_type='DagProcessorJob' order by start_date desc;
206 | | running | DagProcessorJob | 2026-06-26 17:33:29.530223+00 | | 2026-06-26 17:37:04.932384+00 | | airflow-dag-processor-5df45489f7-92r7z | airflow

airflow jobs check --job-type DagProcessorJob
No alive jobs found

It seems that maybe the dagProcessor is not sending a heartbeat?

Guessing this is because the heartbeat is only_if_necessary

airflow/airflow-core/src/airflow/jobs/dag_processor_job_runner.py

Line 55 in ba8cfe4

only_if_necessary=True,

Maybe due to the config option
scheduler.job_heartbeat_sec: 30