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

   ### Apache Airflow version
   
   2.6.0
   
   ### What happened
   
   After upgrading Airflow to 2.6.0 from 2.5.1
   
   We are losing the previous tasks on the Airflow web server GRID . These 
tasks are executed correctly however they are not displayed.
   
![image](https://github.com/apache/airflow/assets/122443108/917eae4a-5f06-48e4-a632-2673ccab635d)
   
   The behavior is curious, since the previous tasks are finished. An example 
is that if I mark the last one as Failed. The Grid is updated and shows me the 
tasks again.
   
   
![image](https://github.com/apache/airflow/assets/122443108/4e4233f0-a938-44d1-aec6-00d1af9ba3c8)
   
   Also if I select this option. You can see that the tasks are found, but they 
are never shown.
   
   
![image](https://github.com/apache/airflow/assets/122443108/b299b9ac-ff00-4d86-9647-d82f5c466940)
   
   But finally I do not do a clear or anything, mysteriously the tasks in the 
Grid are loaded correctly (sometimes are loaded with the correct state 
"sucessfull" other time as in the image without any state)
   
   
![image](https://github.com/apache/airflow/assets/122443108/dbe2cc4a-05f7-401f-b0a7-58a09d205fea)
   
   As you can see in the image, all the task are 'found' but not loaded on the 
grid. Even all the previous task are finished succesfully.
   
   
   We are also seeing other behavior. Since we 'lose' the previous tasks, the 
DagRuns never finish and this results in the next DagRuns never being executed. 
That is, our Dummy task (Start) is not launched because since we do not have 
the previous tasks, we do not have their states.
   
   
   ### What you think should happen instead
   
   All the task should be displayed correctly with their correct state
   
   ### How to reproduce
   
   We don't know, we have days where all the DagRuns are with their correct 
tasks and status. Other cases where having the DAG correctly starts to go wrong 
and we end up losing the tasks. And other cases where nothing is affected.
   
   
   ### Operating System
   
   "Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" 
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-amazon==8.0.0
   apache-airflow-providers-celery==3.1.0
   apache-airflow-providers-cncf-kubernetes==6.1.0
   apache-airflow-providers-common-sql==1.4.0
   apache-airflow-providers-docker==3.6.0
   apache-airflow-providers-elasticsearch==4.4.0
   apache-airflow-providers-ftp==3.3.1
   apache-airflow-providers-google==10.0.0
   apache-airflow-providers-grpc==3.1.0
   apache-airflow-providers-hashicorp==3.3.1
   apache-airflow-providers-http==4.3.0
   apache-airflow-providers-imap==3.1.1
   apache-airflow-providers-microsoft-azure==6.0.0
   apache-airflow-providers-mysql==5.0.0
   apache-airflow-providers-odbc==3.2.1
   apache-airflow-providers-postgres==5.4.0
   apache-airflow-providers-redis==3.1.0
   apache-airflow-providers-sendgrid==3.1.0
   apache-airflow-providers-sftp==4.2.4
   apache-airflow-providers-slack==7.2.0
   apache-airflow-providers-snowflake==4.0.5
   apache-airflow-providers-sqlite==3.3.2
   apache-airflow-providers-ssh==3.6.0
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   _No response_
   
   ### Anything else
   
   After upgrading from 2.5.1 to 2.6.0
   
   ### 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