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

   ### Apache Airflow version
   
   Other Airflow 2/3 version (please specify below)
   
   ### If "Other Airflow 2/3 version" selected, which one?
   
   2.10.4
   
   ### What happened?
   
   We created a DAG, scheduled with 16 different datasets. It ran properly for 
a couple of days, waiting for all 16 datasets to be produced. But suddenly, it 
was triggerred ignoring one dataset (triggered taking into account 15/16 
datasets).
   
   <img width="945" height="630" alt="Image" 
src="https://github.com/user-attachments/assets/f26b008a-1703-4eab-8c3c-17d3b4fe341b";
 />
   <img width="617" height="443" alt="Image" 
src="https://github.com/user-attachments/assets/b839ef5d-ca97-45ff-b7ee-56518d492c2d";
 />
   <img width="1833" height="592" alt="Image" 
src="https://github.com/user-attachments/assets/8827edcc-2d25-4691-bd4d-9d451570b299";
 />
   
   ### What you think should happen instead?
   
   The DAG should not be triggered, since only 15 out of 16 datasets were 
produced at that time.
   
   ### How to reproduce
   
   We cannot reproduce it, it did not happen earlier and we haven't faced it  
again some days later.
   
   ### Operating System
   
   Debian 12
   
   ### Versions of Apache Airflow Providers
   
   No relevant providers used
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Deployment details
   
   We use an AKS cluster in combination with customized docker image, built 
from the official docker image.
   
   ### 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