#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 Are you sure this issue hasn't been raised already? • Yes Have you read the Code of Conduct? • Yes flyteorg/flyte