New RunLLM response generated: >>>*# Question* 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?) # Answer Flyte can handle deep graphs using dynamic workflows, but there are limitations on recursion depth to ensure system stability, as noted in the Merge Sort example. For workflows with many iterations, consider using dynamic workflows with caution regarding depth. Eager workflows are an alternative, but they require specific configurations for remote execution, including

@eager(remote=...)

and secret management, as discussed in this GitHub issue. Eager workflows are still evolving, and their stability may vary depending on your setup. Would you like more detail on either approach? Sources: - Merge Sort example - this GitHub issue Slack Link https://.slack.com/archives/CP2HDHKE1/p1731092634.481269 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.