New RunLLM response generated: >>>*# Question* Hello Everyone! I am trying to execute a launchplan with pyflyte and I have encountered two issues: 1. I am able to execute a launchplan even if it is disabled. I am not sure if this is the expected behavior. If this is expected, then how do I pause the pipeline? 2. When I set a launchplan to an older version (like a rollback), the workflow executes with the latest version and not the active version. Both of these issues seem like bugs, either in the Flyte server or in pyflyte. Can someone clarify the expected behaviors? # Answer 1. Executing a Disabled Launch Plan: According to Flyte Issue #1354, Flyteadmin should not allow launching an execution for a launch plan in an archived (disabled) state. This is a known issue, and the expected behavior is that executions should not proceed if the launch plan is archived. To pause the pipeline, you should deactivate the launch plan using

flytectl

or the Flyte UI. 2. Executing with the Latest Version Instead of the Active Version: When you set a launch plan to an older version, it should execute with the specified version, not the latest one. This behavior is not expected and might indicate a bug. According to Flyte Issue #3109, only one version of a launch plan can be active at any given time, and activating a new version should deactivate the others. Ensure you are explicitly activating the desired version using

flytectl

. Would you like more details on how to deactivate a launch plan or ensure the correct version is activated? Sources: - Flyte Issue #1354 - Flyte Issue #3109 Slack Link https://.slack.com/archives/CP2HDHKE1/p1728517096.008409 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.