#267 [Feature] Prevent concurrent execution Issue created by art4ul Motivation: Why do you think this is important? In my project I use scheduled launch plan to process a dataset each 1 hour. But sometimes the workflow may process the data more the 1 hour. In this case the scheduler creates the new concurrent execution of the launch plan. But the concurrent execution of the job is unacceptable for my use case (I get dublicated output). Goal: What should the final outcome look like, ideally? I think it would be nice to have an option for launch plan to allow concurrent execution or not. Describe alternatives you've considered The only one option fo me to start implementing some distributed locks using some external systems like Zookeeper Flyte component ☐ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☐ FlytePropeller ☐ FlyteIDL (Flyte specification language) ☑︎ Flytekit (Python SDK) ☐ FlyteAdmin (Control Plane service) ☐ FlytePlugins ☐ DataCatalog ☐ FlyteStdlib (common libraries) ☑︎ FlyteConsole (UI) ☐ Other Is this a blocker for you to adopt Flyte Yes flyteorg/flyte

#267 [Feature] Prevent concurrent execution Issue closed as not planned by github-actions[bot] flyteorg/flyte