Channels
announcements
ask-the-community
auth
conference-talks
contribute
databricks-integration
datahub-flyte
deployment
ecosystem-unionml
engineeringlabs
events
feature-discussions
flyte-bazel
flyte-build
flyte-console
flyte-deployment
flyte-documentation
flyte-github
flyte-ui-ux
flytekit
flytekit-java
flytelab
great-content
hacktoberfest-2022
helsing-flyte
in-flyte-conversations
introductions
jobs
konan-integration
linkedin-flyte
random
ray-integration
ray-on-flyte
release
scipy-2022-sprint
sig-large-models
workflow-building-ui-proj
writing-w-sfloris
Title
p
Paul Dittamo
12/17/2021, 9:22 PMHello 👋 is there a way to avoid starting a new scheduled workflow if the previous one is still running?
g
George Snelling
12/17/2021, 10:52 PMHi Paul, I assume you've looked at nested workflows already:
https://docs.flyte.org/projects/cookbook/en/latest/auto/core/control_flow/subworkflows.html#sphx-glr-auto-core-control-flow-subworkflows-py
d
Dan Rammer (hamersaw)
12/17/2021, 10:56 PMHi @Paul Dittamo, currently there is no support to serialize a workflow execution. There are a number of issues (e.x., 267 , 420 ) that deal with this. We have had some preliminary discussions about how this might be done, but haven't finalized a spec / implementation and scheduled the work to be done. If you have ideas and / or are interested in contributing, we are very happy to collaborate on this. It is certainly functionality that many users are interested in.