Hi Flyte team, I need help debugging a stuck workflow. This workflow is stuck for 30+ hrs, its not executing, but the Python Task has status

UNKNOWN

and the sub-workflow that contains that task has status

RUNNING

. Seems like a similar issue was reported here https://github.com/flyteorg/flyte/issues/3536 . Any pointers on what could be wrong here?

We had a similar issue when our datacatalog was deployed incorrectly for cached tasks.

The "phase" column in

flyteadmindb.task_executions

for this task shows "SUCCEEDED", workflow status is "FAILED", but the flyte console UI shows that this task is still running. Could this be a bug in flyte console? Is there anything we can do to fix this?

@wonderful-continent-24967 sounds like a console issue. Could you share the flyte and flytekit versions you're using and a reproducible example?

We were on flyte 1.11 (same flytekit) when this workflow was triggered , but we upgraded flyte backend to 1.15 (8 days after the workflow start time). Unfortunately, we are not able to reproduce this issue, didn't occur again for the same workflow. Also created a github issue for this - https://github.com/flyteorg/flyte/issues/6442