uranusjr commented on issue #55515: URL: https://github.com/apache/airflow/issues/55515#issuecomment-3489936804
Looks like the problem is in how the front end calculates which events are pending https://github.com/apache/airflow/blob/3bb724f0c9592ac7586ab10ec6cc23496424747b/airflow-core/src/airflow/ui/src/pages/DagsList/AssetSchedule.tsx#L44-L47 This simply checks for events created after the last dag run, but really it should check against the dag run _that had process asset events_. Instead of trying to calculate this against the last dag run (however “last” is defined), it might be easier if this uses `getDagAssetQueuedEvents`? But that endpoint would require the frontend to do some extra calculation so potentially multiple events from the same asset are not calculated more than once. I don’t know. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
