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

Flyte

Screenshot 2026-03-19 at 8.03.00 PM.png

We are seeing an issue in Flyte 1.15.1 - dynamic sub-workflow gets stuck in `RUNNING` phase even though all sub tasks have completed (succeeded/failed/skipped).
Is this a known issue that is addressed in subsequent releases?

This can only happen if there is a network problem between dataplane and control plane

Of course 1.15 is very old maybe like 1.5+ years so many things have been fixed