Skip to content

The grid does not refresh with the new dag run when triggered in UI #52907

Closed

Description

@potiuk

Apache Airflow version

Other Airflow 2 version (please specify below)

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

3.0.3rc3

What happened?

When you trigger a DAG via UI, the grid does not refresh to show the new dag run, you need to refresh the page manually so that the new dag run shows up, and once you do it, states of tasks are automatically refreshing.

You can see it in this video: https://drive.google.com/file/d/1VbQ_464jWPFwxIyM5FC44kTP6q-2L6oo/view?usp=drive_link

What you think should happen instead?

I think after triggering the dag, the grid should get refreshed with the new dag run right after, so that you can start seeing the progress of your triggered dag run immediately, without having to click refresh button.

How to reproduce

Build release packages as described in "verify by PMC members" chapter:
https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOW.md
Build task-sdk in similar fashion

Run:

breeze start-airflow --use-airflow-version wheel --use-distributions-from-dist --distribution-format wheel --load-example-dags --load-default-connections

Go to "complex" dag and trigger it.

You should see behaviour similar to https://drive.google.com/file/d/1VbQ_464jWPFwxIyM5FC44kTP6q-2L6oo/view?usp=drive_link

Operating System

Mac OS

Versions of Apache Airflow Providers

  • no providers - only pre-installed once that are coming with airflow installation

Deployment

Other

Deployment details

Breeze

Anything else?

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Activity

  1. potiuk commented on Jul 5, 2025

    @potiuk
    MemberAuthor

    Video also uploaded here:

    Screen.Recording.2025-07-05.at.15.11.46.mov
  2. added
    area:UIRelated to UI/UX. For Frontend Developers.
    on Jul 5, 2025
  3. tirkarthi commented on Jul 5, 2025

    @tirkarthi
    Contributor

    There were some grid optimisations done in main and backported. This is reproducible in main branch too. Probably some key is not being invalidated for the query. I am checking on this.

  4. tirkarthi commented on Jul 5, 2025

    @tirkarthi
    Contributor

    I have created #52918 as a fix. cc: @dstandish @pierrejeambrun @bbovenzi

  5. vatsrahul1001 commented on Jul 6, 2025

    @vatsrahul1001
    Contributor

    Thanks, @tirkarthi for the quick fix. I have verified this in the main now works fine now.

  6. tirkarthi commented on Jul 6, 2025

    @tirkarthi
    Contributor

    Thanks @jscheffl , @potiuk and @vatsrahul1001 for the quick review and testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:UIRelated to UI/UX. For Frontend Developers.area:corekind:bugThis is a clearly a bugneeds-triagelabel for new issues that we didn't triage yet

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions