A second question: I'd like to construct a workflow that's like a while loop, in which the body is a task. It looks like I could do that with a dynamic workflow with recursion, like in https://docs.flyte.org/projects/cookbook/en/v0.3.66/auto/core/control_flow/run_merge_sort.html If there are e.g. 100s of iterations, this can lead to very deep graphs. Can flyte handle that? Or should I use eager workflows for this application? (if so, how stable are these?)

Eager is being worked on right now. We believe by eoy, we will have a more stable version of eager. Auth is the problem for eager For dynamic 100 levels deep should work, challenge might be visualization

Okay, thanks, that's very helpful. Would there be another pattern to create a while loop-like control flow with dynamic workflows?

No dynamic is the way, you can always launch child workflows nested

Thanks! Will definitely try