Hi. I am interested in how Prefect approaches the concept of nested or sub flows. That is running a flow inside another. I’ve not found anything in the docs about this?
Or is this a design pattern that Prefect discourages? Thank you.
Thank you. I hadn’t found that page yet. That’s definitely very relevant.
I can see how I could write a task to start a flow and include that task inside a flow. We are migrating some workflows, from another system, which iterates over rows of data and starts a new “flow” for each. But I was wondering if that’s an anti-pattern in Prefect.
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.