slords opened a new issue, #41101:
URL: https://github.com/apache/airflow/issues/41101

   ### Apache Airflow version
   
   Other Airflow 2 version (please specify below)
   
   ### If "Other Airflow 2 version" selected, which one?
   
   2.9.2
   
   ### What happened?
   
   We have an airflow environment in AWS (MWAA).  We have multiple DAGs that 
are triggered based on a number of datasets.  In 2.8.1 everything was working 
fine.  After upgrading to 2.9.2 some of the DAGs are triggering without all the 
datasets updates being met.  Sometimes they work and other times they don't.  
If there is logging (or DEBUG logging) that can be enable to troubleshoot this 
more please provide links to information and I'll try and provide more 
information.
   
   ### What you think should happen instead?
   
   DAGs should only be triggered when all the Datasets have updates since the 
last time the DAG ran.
   
   ### How to reproduce
   
   There isn't anything we can do to trigger this issue.  We have 1100 DAGs, 
600+ of which are triggered by Datasets.  Of these we have 40-50 that fail 
nightly.  They aren't the same DAGs or Datasets that are having issues.  As 
mentioned above if there are logs or debugging that can be collected to provide 
better information or reproducibility I'd be glad to enable and collect the 
needed information.
   
   ### Operating System
   
   AWS MWAA 2.9.2 (latest)
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Amazon (AWS) MWAA
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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