Hi Flyte team! I'm wondering how I should interpret

UNKNOWN

states in a workflow. This is a sub-workflow under a dynamic workflow. It ran for 7h 50m, and while its status is shown as

SUCCEEDED

and we are able to get its input and output, all of its tasks and sub-workflows are shown as

UNKNOWN

and doesn't display any input/output. Querying

flyteadmindb

shows no information of the node, neither the

SUCCEEDED

sub-workflow nor the nodes under it. But it also doesn't look like it's not executed. Any pointers on what could be wrong here?

@hallowed-toothbrush-42565 did it came from a recovered execution?

@average-finland-92144 No it's not

Most of the times

UNKNOWN

means

Not Started

Hi @average-finland-92144 , I'm certain that's not the case since the user is able to get execution logs of these tasks from wandb, so the tasks were executed, but the status is not logged properly to FlyteAdmin's database. Do you think this is worth opening an issue? In addition this is on Flyte 1.15.

do you think it's similar to this issue? https://github.com/flyteorg/flyte/issues/6442 If so I'd ask you to comment and add a thumbs up reaction to signal priority

There's some difference. The previous one is about Flyte console being inconsistent with

flyteadmindb.task_executions

. In this case Flyte console is consistent with

flyteadmindb

but the latter failed to store the status of the tasks.