hey so im working on my first real flow as part of a POC for my org and im just trying to wrap my head around what the tradeoffs are in regards to a flow of flows or one big flow. We have a lot of already made tasks and im not sure if making too many flows will cause issues in the long run or of having one huge flow will have its own problems. Any thoughts on what the tradeoffs are and how one should go about balancing against the two?

Hi @joshua mclellan, I guess this depends on our dependent those small flows are. Passing data between subflows is not quite first class yet and you need to persist the data in the upstream flow before loading it in a downstream flow. On the other hand, one large flow can run into issues with memory management. One very cool application of subflows I have seen is the swapping out of the Executor where you can have high memory instances for one subflow, and then high compute instances for another flow. In terms of logging, logs of the subflows don’t appear in the main flow. You would have to go to the subflow triggered in order view the logs. If you build a Docker container for the flow, having the large flow means you have to re-build everything (might be a big deal) while the flow of flows kind of provides more modular components. The flow of flow lets you edit and re-register flows more granularly.