Airflow 3.0.2: Airflow Graph UI not rendering task state colors.

[arunangshu01]

Apache Airflow version

3.0.2

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

No response

What happened?

I have been using Airflow 3.0.2 for my own data-engineering-pipeline code. After running the DAG, I am noticing that the graph is not rendering the task states colors even after refreshing the page.

Note: I am using a dynamically generated DAG using loops.

What you think should happen instead?

State Colors should reflect on the DAG Tasks while the DAG is in running state.

How to reproduce

From the second trigger itself when the configs are uploaded.

Operating System

linux

Versions of Apache Airflow Providers

apache-airflow==3.0.2
apache-airflow-providers-apache-beam==6.0.4
apache-airflow-providers-google==15.1.0
apache-airflow-providers-snowflake==6.3.1
apache-airflow-providers-postgres==6.2.0
apache-airflow-providers-redis==4.1.0
apache-airflow-providers-common-sql==1.27.1
google-cloud-bigquery-storage==2.32.0

Deployment

Docker-Compose

Deployment details

Docker Compose version v2.28.1

Anything else?

Nothing

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.

[manoj-ia]

facing the same issue @bbovenzi

[arunangshu01]

Hi. Is there any workaround for this?

[bbovenzi]

I would need to debug. Is there an example dag you can provide to replicate this issue?

[arunangshu01]

from airflow.sdk import DAG
from airflow.providers.standard.operators.python import PythonOperator
from airflow.sdk import Variable
import pendulum
from datetime import timedelta
import time
import ast

default_args = {
    'owner': 'airflow',
    'retries': 5,
    'retry_delay': timedelta(minutes=1),
}

def set_list_variable(**kwargs):
    Variable.set('sample_list', str(list(range(1, 1500))))

def get_list():
    val = Variable.get('sample_list', default='[1]')
    return ast.literal_eval(val) if isinstance(val, str) else val

def iterator_task(i, **kwargs):
    print(f"Processing item {i}, sleeping for 2 seconds")
    time.sleep(2)

def iterator_task1(i, **kwargs):
    print(f"Processing item {i}, sleeping for 2 seconds")
    if isinstance(i, str):
        raise Exception
    time.sleep(2)

def final_task(**kwargs):
    print("All iterator tasks are done.")

with DAG(
    'dynamic_sequential_dag',
    default_args=default_args,
    description='DAG with variable-driven dynamic tasks (classic loop)',
    schedule=None,
    start_date=pendulum.datetime(2023, 1, 1, tz="UTC"),
    catchup=False,
    tags=['example'],
) as dag:

    t1 = PythonOperator(
        task_id='set_list_variable',
        python_callable=set_list_variable,
    )

    t2 = PythonOperator(
        task_id='task_2',
        python_callable=iterator_task,
        op_args=[2],
    )

    tasks = []
    for i in eval(Variable.get('sample_list', default='["dummy"]')):
        task = PythonOperator(
            task_id=f'iterator_task_{i}',
            python_callable=iterator_task1,
            op_args=[i],
            retries=5,
        )
        tasks.append(task)

    t3 = PythonOperator(
        task_id='final_task',
        python_callable=final_task,
    )

    t1 >> t2 >> tasks >> t3

Here is the example dag, @bbovenzi
You have to keep on trying to replicate the issue.

[manoj-ia]

@bbovenzi my usecase is also similar i have a dynamic dag, where one of the initial task sets the configuration and later on one of the configuration i have written a for loop. Since the configuration is a airflow variable it has a dummy value at the start, so when the dag is parsed its parsed with dummy value and V1 version is tagged. After triggering the dag the configuration gets updated and the dynamic tasks are generated in the for loop so the version V2 gets tagged and the DAG either fails or when it retries the the new graph gets rendered based on the dynamic configuration and no status colors are visible

[vatsrahul1001]

@arunangshu01 I verified this in 3.0.3, and state color does show you need to select the specific Dag run.

Screen.Recording.2025-07-29.at.12.30.49.PM.mov