Hi Flyte Community!! I am running workflow via LaunchPlan(..., CronSchedule("*/45 * * * *")...). Sometimes a workflow run can take than 45mins. How to make sure a LaunchPlan can run with single wf execution? I am okay with skipping or pending the new workflow execution by LaunchPLan.

I don’t believe there is support for this yet: https://github.com/lyft/flyte/issues/267

Maybe is this the workaround? https://github.com/flyteorg/flyte/issues/872 ?

If an execution is triggered by a launch plan with the same arguments and caching is enabled wouldn’t the execution just result in a noop since the task outputs are cached?

Discussed offline; our tasks returns None, hence not getting cached but cache_serialize=True makes tasks execution concurrently. This unblocks us, but it would be nice to fix https://github.com/lyft/flyte/issues/267.

This is being worked on now by LinkedIn- please collaborate

Thanks @freezing-airport-6809!! I have a few follow-up questions regarding the current implementation. Specifically, I'm curious about how the scheduler selects the next queued task when

cache_serialize=True

. For instance, if taskA is running and taskB, taskC, and taskD are queued, which task will the scheduler choose for execution once taskA is finished?