#6442 [BUG] Inconsistency in Flyte console UI Issue created by ababbar-stripe ### Describe the bug We have a workflow that has failed, but some sub-workflows are stuck in Running status for 400+ hr. The child Python Tasks have status UNKNOWN. The

phase

column in

flyteadmindb.task_executions

for this task (sub-workflow) shows

SUCCEEDED

, workflow status is

FAILED

, but the flyte console UI shows that this task (sub-workflow) is still running. We were on flyte 1.11 (same flytekit) when this workflow was triggered , but we upgraded flyte backend to 1.15 (1 week after the workflow start time). Could this be a bug in flyte console? Is there anything we can do to fix this? ### Expected behavior Flyte console should show the same status as

flyteadmindb.task_executions

### Additional context to reproduce No response ### Screenshots [Image](https://private-user-images.githubusercontent.com/195055764/441006529-218c0e7d-eb08-46e2-9d9a-ceb4f6e0bfa3.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjQwNjUxMzAsIm5iZiI6MTc2NDA2NDgzMCwicGF0aCI6Ii8xOTUwNTU3NjQvNDQxMDA2NTI5LTIxOGMwZTdkLWViMDgtNDZlMi05ZDlhLWNlYjRmNmUwYmZhMy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUxMTI1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MTEyNVQxMDAwMzBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04YjZkMDZiNTRmZTVkMTY3NTY0MWNiMWUzNTk2NGJmOTA0OWU5YmJhNmFkN2ZlNGMzMzg4ZGRmODdhNWVmOGY5JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.k76LSSEFmcRCu9P2yP0tan_NEUZqpZ_MMXQnWoB9ti8) ### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte