Long delay in "queued" state before DAG tasks start running

[ANBUPRIYA-A-D]

Apache Airflow version

3.0.6

If "Other Airflow 2 version" selected, which one?

No response

What happened?

I am running Airflow and using it to create a code-server container.
When I trigger the DAG, I notice that the task initially stays in the queued state for up to ~20 seconds before moving to the running state.
Observed behavior:
DAG is triggered successfully. Task stays in queued state for ~20 seconds. After that delay, it transitions to running and executes normally.
Steps to reproduce:
Trigger a DAG that creates a code-server container. Observe the task state transition in the Airflow UI.
Environment:
Airflow version: 3.0.6
Executor type: KubernetesExecutor
Deployment: Helm

What you think should happen instead?

No response

How to reproduce

Task should transition from queued → running as quickly as possible (minimal delay).

Operating System

NAME="Red Hat Enterprise Linux" VERSION="8.10 (Ootpa)"

Versions of Apache Airflow Providers

No response

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

[boring-cyborg[bot]]

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.

[cadis3419]

Hey, did you find a solution? I’m experiencing the same issue with Airflow 3.0.6.
When I trigger a DAG from the terminal, it starts immediately. However, when I trigger it via the UI or let it run on schedule, there’s a delay of about 3 minutes before it starts.
I’ve already tried adjusting several scheduler and DAG processor configurations, but the behavior is still the same.