hello, flyte team. I have a question about workflow register process. I am currently automating ML process through flyte with github CI, and I have problem, launchplan deactivation. The workflow successfully registered in flyte, but it does not show DAG and users cannot start "launch" in console. where do I check log? I hope to get some advice. thanks

Hi, @SeungTaeKim! Can you try hitting

https://<url_domain>/api/v1/workflows/<project>/<domain>/<wf>/<version>

?

That is the problem because I cannot see any execution ID from the workflow (it is registered, but never executed now)

Sorry, use version, not execution ID. ^ Modified the URL.

oh, I try right away

I think the version somehow doesn’t exist.

Hi @SeungTaeKim what command did you use to register your workflows . And also can you use flytectl to get the workflow and see if they are archived. Archived workflows cannot be launched and hence might be showing as disabled .

some of workflow I executed before is working well,,, I think it is other problem.

Can you try this command on your workflow

flytectl update workflow-meta -p flytesnacks -d development flyte_project_template.mlflow_flyte_test.mlflow_wf --activate

It has returned

unknown flag

. Are you talking to the commands like

workflow-execution-config

or

workflow-meta

??

sorry workflow-meta

got it, hang on a second

what command did you use to register and are you using the right project/domain

my team use github action CI with the codes below.

- name: Create project
        run: |
          flytectl create project --name ${{ env.FLYTE_PROJECT }} --id ${{ env.FLYTE_PROJECT }} || true
           if [ !-z "${{ env.FLYTE_DESCRIPTION }}" ]; then
            flytectl update project -p ${{ env.FLYTE_PROJECT }} --description ${{ env.FLYTE_DESCRIPTION }}
           fi

      - name: Archive launchplans
        run: |
          (flytectl get launchplan -p {{ $env.FLYTE_PROJECT }} -d {{ $env.FLYTE_DOMAIN }} -o json || echo "") | jq -rc 'if type=="array" then map(.id)[] else .id end' | while read id; do
              name=$(echo $id | jq -r .name)
              version=$(echo $id | jq -r .version)

              flytectl update launchplan $name -p ${{ env.FLYTE_PROJECT }} -d ${{ env.FLYTE_DOMAIN }} --version $version --archive
          done

      - name: Serialize project
        run: |
          mkdir _pb_output
          echo pyflyte --pkgs ${{ env.PROJECT_NAME }} serialize --local-source-root . --image ${{ env.IMAGE_TAG }} workflows -f _pb_output/
          pyflyte --pkgs ${{ env.PROJECT_NAME }} serialize --local-source-root . --image ${{ env.IMAGE_TAG }} workflows -f _pb_output/

      - name: Register serialized project
        run: |
          flytectl register files _pb_output/* -p ${{ env.FLYTE_PROJECT }} -d ${{ env.FLYTE_DOMAIN }} --version ${{ env.VERSION }}

      - name: Activate launchplans
        run: |
          tomlq -rc '.qraft.flyte.active_launch_plans[]' pyproject.toml | while read name; do
             flytectl update launchplan $name -p ${{ env.FLYTE_PROJECT }} -d ${{ env.FLYTE_DOMAIN }} --version ${{ env.VERSION }} --activate
          done

This might be easier , can we hop on a call and check https://meet.google.com/noo-wzwc-aoe

Oh, I am sorry to say I cannot access the video call now. I am on my office, it's little bit difficult to contact. so thank you to your help 🙂

Ok sure. Np. One thing i wanted to check more here is how the UI is pulling the same workflows in the UI then if cli is throwing those errors . which leads me to check if the parameters of project and domain are right

I have checked the project name different,

flytesnacks

into

flyte-project-template

, and CLI returns

successfully updated

. but the the launch plan button is still deactivated

Hmm that’s strange .Would mind creating this execution from cli and will add UI team to check more on this .

Great. I try the process I did with CLI and said you the result

@SeungTaeKim, are you seeing the same result with CLI?

@Samhita Alla yeah, troubling with the same one, I am still searching solutions

@SeungTaeKim, can you try by getting the launchplan first and then updating it?

flytectl get launchplan -p <project> -d <domain> <wf>

flytectl update launchplan -p <project> -d <domain> <name_of_lp> --version <version> --activate

Just wondering if launch plan + version flag would work.

@SeungTaeKim what was the result of the cli execution .

I haven't found the solution yet. The whole result I saw is

Not Found

, so I guess Flyte admin does not found the registration file (The path is registered with CLI, but not file) I think I should check where the filed gone tomorrow