@ancient-wolf-19325 I'm having an issue updating launchplans and workflows in the flyte console. I'm running

pyflyte register ...

and everything is running fine, and it shows a new version and everything, but then the new launchplan doesn't show up when I go to workflows and click on Launch Workflow. It shows the previous launchplans, but not a new one that I just added to the code using

LaunchPlan.get_or_create(...)

and the new version doesn't seem to show up there. If I go to the launchplans page, I do see it there, but its not being attributed to the workflow

It seems like the issue might be related to how Flyte handles the registration and display of launch plans in the console. According to this GitHub issue, there can be discrepancies in the Flyte console where the execution console shows old workflow names even after updating the launch plan to a new workflow. This might be due to caching mechanisms or how the Flyte UI fetches and displays data. To ensure that the new launch plan is correctly attributed to the workflow, you can try the following steps: 1. Register Tasks and Workflows Separately: Use the

pyflyte register

command with the

--tasks-only

and

--workflows-only

options to register tasks and workflows separately before registering the launch plans. 2. Register Launch Plans: Use the

--launchplans-only

option to register the launch plans. Here are the commands:

# Register tasks
FLYTE_SDK_LOGGING_LEVEL=20 pyflyte register --non-fast -p <project> --domain <domain> <path_to_file> --version <version> --tasks-only

# Register workflows
FLYTE_SDK_LOGGING_LEVEL=20 pyflyte register --non-fast -p <project> --domain <domain> <path_to_file> --version <version> --workflows-only

# Register launch plans
FLYTE_SDK_LOGGING_LEVEL=20 pyflyte register --non-fast -p <project> --domain <domain> <path_to_file> --version <version> --launchplans-only

This approach ensures that the tasks and workflows are registered before the launch plans, which might help in correctly attributing the launch plans to the workflows. Would you like more detail on this process or any other aspect of Flyte? Sources: - After updating launchplan to a new workflow, breadcrumbs of execution console shows old workflow name - Launch Plan Registered Twice 👍 0 button 👎 1 button 💡 Hint: Mention @ancient-wolf-19325 in the thread for followups.

@big-notebook-82371 so can you share exactly how you created the launchplan? I think there's a difference between

LaunchPlan.get_or_create(workflow=my_wf)

which creates the default launchplan, that doesn't accept certain parameters and `

launch_plan.LaunchPlan.get_or_create

that requires you to name it but accepts other parameters Not sure if that's tied to this strange behavior in the UI though

Hey David, I ended up figuring it out in the community channel! It ended up being a directory path change that caused the issue.. so I'm going in the right direction now

I ended up figuring it out in the community channel

yeah! just saw it. Glad it works now