further investigation i found that
Currently creating circular loops in the Journey Canvas is not supported. This is enforced at canvas level due to reasons listed below.
The execution engine is built around a DAG (Directed Acyclic Graph) model: profiles move forward through nodes; they don’t orbit around them.
Allowing authors to connect any node back to a previous node creates several hard‑to‑control risks:
• Infinite or near‑infinite loops if the exit condition is incomplete, misconfigured, or data doesn’t change as expected.
• Reporting and Metrics data would be skewed/inaccurate
Unbounded dwell times for profiles inside a journey, which breaks assumptions around:
• Global journey timeout
• Re‑entrance rules
• Capacity planning and throttling
This is called the internal loop design as “forbidden patterns” (single-node loops on conditions/waits/end, loops within loops, entangled loops, etc.) because these patterns are often easy to misconfigure.