Is it possible that flyteconsole can get confused ...
# flyte-console
b
Is it possible that flyteconsole can get confused with subworkflow executions? Here's an example. I have two workflows called data_prep and train and then another workflow that runs both as subworkflows. So we have nodes n0 for data_prep and n1 for train and the tasks are named n0-0-n0, n0-0-n1... for data_prep and n1-0-n0, n1-0-n1 for train. But it seems flyteconsole mixes things up in the execution view:
In reality first subworkflow only contains data_prep tasks while the second one only contains train/eval tasks. The UI shows these tasks mixed up.
👀 1
l
Okay let me take a look
Quick question though - which version of
flyteconsole
are you running? Asking because this was a known issue but we thought we fixed it
b
Ah sorry forgot to mention I’m already on the latest release
0.36.0
(I did an upgrade to check if it would make any difference)
l
hey I am also facing the same problem here, ui version is 0.4 cc @most-gold-65483
c
Hi @late-fish-63527, thanks for reporting. Good news: it is a fully flyte-console UI issue, which means your workflows are executed the way you have set them up. Not so good news: We have a partial fix in PR which plan to be merged this week. We will notify this thread with the flyte-console version when the fix would be in. It will properly resolve entities in case if the parent noteId differs, but will still got confused on grand parent and deeper level of comparison. Unfortunately full fix will require some more substantial infrastructure change, which are planned by, but we don’t have a specific ETA at this time.
@late-fish-63527 @boundless-pizza-95864 The partial fix for this issue was just merged to flyte-console. Full fix will require some infrastructure changes, so we can not yet provide expected timeline for the fix. This issue has been resolved in version 0.42.1 🎉 The release is available on GitHub release
🎉 2