Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Hello :wave:  is there a way to avoid starting a new scheduled workflow if the previous one is still running?

Hi 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>

Hi <@U021MRR48LU>, currently there is no support to serialize a workflow execution. There are a number of issues (e.x., <https://github.com/flyteorg/flyte/issues/267|267> , <https://github.com/flyteorg/flyte/issues/420|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.

I should note that we have implemented similar (but not exact) functionality exists for cachable tasks (issue <https://github.com/flyteorg/flyte/issues/872|872> ). The cache_serializable API (<https://github.com/flyteorg/flyte/blob/master/rfc/core%20language/1461-cache-serialize-api.md|rfc> ) is in the final throes of testing, but should be available in the next release.