MartinEmilJakobsen commented on issue #53817:
URL: https://github.com/apache/airflow/issues/53817#issuecomment-3180409781

   @pierrejeambrun 
   
   Exactly how long before the cache is invalidated/stale? Can you help me 
understand how to help force an invalidation?
   
   I just tried to reproduce the issue, I triggered an update to an upstream 
asset at 19:19:47, as seen below.
   
   
![Image](https://github.com/user-attachments/assets/88e5a061-8d79-4ed1-a715-7eab751d544f)
   
   Then I REST API to delete queued asset events for the above asset-scheduled 
downstream DAG above at 19:27:39. Since the REST API call I have tried 
refreshing (in chrome f5), deleting cookies, logging in and out, or restarting 
entire browser, but as of 19:51 the cache has not been invalidated yet, i.e., 
almost 25 minutes without invalidation. 
   
   The last time I tried to reproduce this issue, it did invalidate the cache 
until the DAG received all required asset update events all over again to 
trigger the DAG-run.
   
   


-- 
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]

Reply via email to