Hey! I'm having an issue with registering launchplans, and having them show up connected to a workflow. I'm adding a new launchplan for a workflow using

LaunchPlan.get_or_create(...)

, then running

pyflyte register path/to/workflow.py -p project -d domain

. Everything runs fine, and it shows the new version string. In the flyte console, I can see the launchplan itself in the Launch Plans tab with the new version, but when I go to the workflow in the Workflows tab, and click Launch Workflow, its only showing older versions in the Workflow version dropdown, and the new launchplan isn't shown in the Launch Plan dropdown. Is the workflow version the same as the version shown when registering? This only just now seems to be an issue, it was working fine up until recently

the register command should print out all the entities it’s registering

Yeah, so all the

Registration ... LAUNCH_PLAN

and

Registration ... WORKFLOW

stuff prints out. The workflow is there for the overall workflow, and each launchplan that I'd expect to see if there, but then that version of workflow doesn't show up in the console, but it does show up in the launchplans

not entirely following… would you mind copy/pasting the register output (redact names if you want)

Yeah, here's the output

Running pyflyte register from path/to/code with images ImageConfig(default_image=Image(name='default', fqn='<http://cr.flyte.org/flyteorg/flytekit|cr.flyte.org/flyteorg/flytekit>', tag='py3.10-1.13.4', digest=None), images=[Image(name='default', fqn='<http://cr.flyte.org/flyteorg/flytekit|cr.flyte.org/flyteorg/flytekit>', tag='py3.10-1.13.4', digest=None)]) and image destination folder /root on 1 package(s) ('/Users/<user>/dai/code/cybernetics/detector/detector_pipeline.py',)
Registering against <http://flyte.domain.com|flyte.domain.com>
Detected Root path/to/code, using this to create deployable package...
No output path provided, using a temporary directory at /var/folders/fg/rj4k8n6n6gz2mvvsqdv34_1h0000gn/T/tmp_u9v4qpo instead
Computed version is Mxuji6SmjvFRo5-uGYS5yg
Loading packages ['detector.detector_pipeline'] under source root path/to/code
Image us-central1-docker.pkg.dev/dai-ml-pipelines/flyte-pipelines/default:QbhpPoJ1HnMIoJtST_44bg found. Skip building.
Image us-central1-docker.pkg.dev/dai-ml-pipelines/flyte-pipelines/gcloud:DHMde3nJznQF0DCOHcCFDA found. Skip building.
Image us-central1-docker.pkg.dev/dai-ml-pipelines/flyte-pipelines/detector_train:aeK6Nv9bo_qYB2HjeKq_FA found. Skip building.
Image us-central1-docker.pkg.dev/dai-ml-pipelines/flyte-pipelines/detector_serialize:URlgVNOdiYdTZ7reC_w7bA found. Skip building.
Successfully serialized 24 flyte objects
[✔] Registration common.tasks.pipeline_setup.get_pipeline_steps type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration common.tasks.pipeline_setup.get_dataset_bucket_dir type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration common.tasks.pipeline_setup.return_float type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration common.tasks.pipeline_setup.create_pipeline_status type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration common.tasks.data_validation.validate_dataset type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration detector.steps.detector_bigquery.setup_detector_bigquery type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration common.tasks.pipeline_setup.return_str type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration common.tasks.pipeline_setup.noop type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration detector.steps.detector_data_processing.process_detector_dataset type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration common.tasks.pipeline_setup.get_output_dir type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration common.tasks.pipeline_setup.return_str_float_tuple type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration common.tasks.deploy.trigger_model_deployment type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration detector.steps.detector_serialize.serialize_detector type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration detector.steps.detector_evaluate.evaluate_detector type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration detector.steps.detector_train.train_detector type TASK successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration detector.detector_pipeline.detector_train_eval_serialize type WORKFLOW successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration detector.detector_pipeline.detector_train_eval_serialize type LAUNCH_PLAN successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration detector.detector_pipeline.detector_pipeline type WORKFLOW successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration detector.detector_pipeline.detector_pipeline type LAUNCH_PLAN successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration x_detector_pipeline_launchplan type LAUNCH_PLAN successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration y_detector_pipeline_launchplan type LAUNCH_PLAN successful with version Mxuji6SmjvFRo5-uGYS5yg
[✔] Registration z_detector_pipeline_launchplan type LAUNCH_PLAN successful with version Mxuji6SmjvFRo5-uGYS5yg

z_detector, the bottom one, is the new launch plan that I added In the Launch Plans tab, I can see the versions of that launchplan showing up, as shown in the first image then the second image shows that on the Workflows tab, there are no new versions showing up, the latest is from over a month ago then when I click Launch Workflow, the new launchplan does not show up, because it only has those old workflow versions where it didn't exist. and I also can't run the updated versions of the existing launchplans

which workflow does

z_detector_pipeline_launchplan

correspond to?

detector.detector_pipeline.detector_pipeline

?

Yeah, here's a modified version of the launchplan in the code

z_launch_plan_name = "z_detector_pipeline_launchplan"
    z_launch_plan = LaunchPlan.get_or_create(
        name=z_launch_plan_name,
        workflow=detector_pipeline,
        default_inputs={
            **default_inputs,
            "epochs": 16,
            "batch_size": 28,
        },
        fixed_inputs={
            "model_type": "detector",
            "model_category": "z",
        },
    )

where

detector_pipeline

is the name of the workflow in the code

so just to clarify… this doesn’t really have to do with the launch plan right?

yeah, I guess its more that the workflow itself isn't updating at all

got it okay

yeah, it isn't there either. the versions go back to january, but the august one is still the latest

and if you click on one… then manually change the version to

Mxuji6SmjvFRo5-uGYS5yg

do you get a 404? (like manually change the url)

oh man.. I think I see the issue. there was a refactor a little bit ago that added a directory in the path to the workflows, and now I'm seeing the new workflow with the new path showing up

oh yeah, should’ve thought of that.

for sure. thanks for the help! that helped me realize that

ofc