#3500 [BUG] Status of Sub-Workflow not being updated correctly. Issue created by stephen37 Describe the bug When a workflow is running with sub-workflows, even if the workflow is in a

Failed

state, the sub-workflows can stay in a

Queued

state in the UI (cf. screenshot) Those are impossible to stop as they are technically not running anymore. Here is the list of pods in the namespace associated with this project.

❯ k get pods 
NAME                        READY   STATUS      RESTARTS   AGE
ajrs5vwphfsx2sj9ldmq-n0-0   0/1     Completed   0          175m
ajrs5vwphfsx2sj9ldmq-n1-0   0/1     Completed   0          175m
ajrs5vwphfsx2sj9ldmq-n2-0   0/1     Completed   0          175m
ajrs5vwphfsx2sj9ldmq-n3-0   0/1     Completed   0          173m
aq8pt9rjwpssjw7whvsq-n0-0   0/1     Completed   0          24h
aq8pt9rjwpssjw7whvsq-n1-0   0/1     Completed   0          24h
avp8s7qxhgtpw7ckz2gv-n0-0   0/1     Completed   0          10h
avp8s7qxhgtpw7ckz2gv-n1-0   0/1     Completed   0          10h
azc4p4n9g9k8q4bdg767-n0-0   0/1     Completed   0          10h
azc4p4n9g9k8q4bdg767-n1-0   0/1     Completed   0          10h

Discussion in Slack with @hamersaw https://flyte-org.slack.com/archives/CP2HDHKE1/p1679075564278029 Expected behavior The UI should also be showing the sub-workflows in

Failed

stage or

Aborted

stage I guess depending on what the real states of the sub-worklows are. Additional context to reproduce No response Screenshots Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte