@ancient-wolf-19325 if I pass

--activate-launchplan

in a

pyflyte register

command on a workflow, it activates the launchplan for that workflow. What does an active launchplan mean. does flyte execution not use the latest launchplan always unless otherwise specified

An active launch plan in Flyte is the version of the launch plan that is currently set to run according to its schedule. When you activate a launch plan, it becomes the one that Flyte will use for scheduled executions, and any previously active launch plan for the same workflow will be deactivated. According to FlyteCTL Feature: Schedule ergonomics, only one version of a launch plan can be active at any given time for a specific project, domain, and launch plan name. Activating a new version will automatically deactivate the previous version. This ensures that only the specified version of the launch plan is used for scheduled executions. If you do not activate a launch plan, it will not be used for scheduled executions, even if it is the latest version. You must explicitly activate the desired version to ensure it is used. Would you like more details? Sources: - FlyteCTL Feature: Schedule ergonomics - Flyte discussion on dynamic launch plans 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 if my workflow will never run on a schedule and will only be run manually, does that mean I do not need to worry about activating launchplans?

Yes, if your workflow will only be run manually and never on a schedule, you do not need to worry about activating launch plans. Activation is primarily for enabling scheduled executions. For manual runs, you can directly trigger the workflow using the default or any specified launch plan without needing to activate it. Would you like more details? Sources: - Flyte Launch Plans - Running Workflows 👍 1 button 👎 0 button 💡 Hint: Mention @ancient-wolf-19325 in the thread for followups.