fix: get the correct schedule for asset-triggered Dags#62868
Merged
bbovenzi merged 1 commit intoapache:mainfrom Mar 4, 2026
Merged
fix: get the correct schedule for asset-triggered Dags#62868bbovenzi merged 1 commit intoapache:mainfrom
bbovenzi merged 1 commit intoapache:mainfrom
Conversation
bbovenzi
approved these changes
Mar 4, 2026
Lee-W
added a commit
to astronomer/airflow
that referenced
this pull request
Mar 5, 2026
Lee-W
added a commit
to astronomer/airflow
that referenced
this pull request
Mar 5, 2026
1 task
Member
There was a problem hiding this comment.
This is creating a lot of noise in the UI:
Is it possible to maybe update the backend endpoint to instead return an empty list when no queuedEvents are found? (list should return empty list, and 404 should only happen when querying a specific event) And update the UI accordingly?
Member
|
Thanks, here is the pr #62934 |
1 task
dominikhei
pushed a commit
to dominikhei/airflow
that referenced
this pull request
Mar 11, 2026
skymensch
added a commit
to skymensch/airflow
that referenced
this pull request
Apr 3, 2026
…umer DAG run The ``next_run_assets`` UI endpoint was not tested for the case where a consumer DAG has never run before. This caused a regression in older versions (3.1.x) where the frontend relied on ``latestRunAfter`` being defined to show queued assets, making the counter always show "0 of N" on the first run cycle. The fix (frontend, PR apache#62868) switched to using ``AssetDagRunQueue`` records via ``useAssetServiceGetDagAssetQueuedEvents`` for the counter, which works correctly regardless of whether a prior run exists. This test ensures the backend correctly returns ``lastUpdate`` for queued assets even when no ``DagRun`` has ever been created. closes: apache#64616 Signed-off-by: Haneul Yeom <haneul0826@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Closes: #55515
The original logic is not accurate. We should get the number of queued events
What
Get the number of queued events instead of depending on the last run which can be a manual one
Was generative AI tooling used to co-author this PR?
cursor
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.