#4716 [BUG] Launching in fast mode from a file containing workflow tasks and launch plans results in an error Issue created by dennisobrien ### Describe the bug We recently upgraded

flytekit

from 1.7.0 to 1.10.2 and since then we have seen an error when launching an execution in fast mode. When we have a python file that contains workflows, tasks, and launch plans and try to run that in fast mode, we get an error: $ python3 workflow.py --inference_date=2024-01-07 --n_days_horizon=180 ╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── Traceback (most recent call last) ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ /.../workflow.py:319 in <module> │ │ │ │ ❱ 319 launch_plan = LaunchPlan.get_or_create( │ │ │ │ /.../lib/python3.10/site-packages/flytekit/core/launch_plan.py:273 in get_or_create │ │ │ │ ❱ 273 │ │ │ │ raise AssertionError("The cached values aren't the same as the current c │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ AssertionError: The cached values aren't the same as the current call arguments The workaround has been to put the launch plan definitions in a separate file from the workflow and task definitions. There are no errors when we run this in non-fast mode. ### Expected behavior Ideally we can include launch plan definitions in the same file as the workflow and task definitions. ### Additional context to reproduce Sorry I don't have a minimal reproducible example, but these are the steps I think will reproduce this. 1. Create an environment using

flytekit==1.10.2

. 2. Create a python file that defines a workflow, at least one task, and at least one launch plan. The launch plan should accept arguments. 3. Run the execution in fast mode from the command line. 4. Assuming you get the same error described above, try moving the launch plan to a separate file. 5. Run the execution from the new file containing only the launch plan. 6. This workaround has worked for us. ### Screenshots No response ### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte