It sounds like one or more of the logic markers at the start of the “C” loop region are active when the timeline playback position reaches the end of the “C” loop region, and, as a result, when the playback is sent back to the start of the “C” loop region, it immediately hits one of the logic markers at that position and is sent by that marker to some other place. From your screenshot, it looks like there are five markers that could be responsible: The “B’” loop region, the “To B” transition marker, the “To B” transition region, the “To B’” transition region, and the “To C” transition region. (I imagine the “To D” transition region has trigger conditions that prevent it from being active at any point when the event is not ending.)
To prevent the timeline playback position from being moved by active logic markers at the start of the “C” loop region, you must ensure that there are no acive logic markers at the start of the “C” loop region when the timeline playback position is there.
The easiest way to do this is to move the start of the “C” loop region away from the end of the “B’” loop region. Moving it two bars to the right should allow you to preserve your existing loop length and quantization behavior.
No. The “C” loop region is moving the timeline playback position to the start of that loop region as expected. The problem is that as soon as it does so, the timeline playback position touches the other logic markers at the start of the “C” loop region, and those logic markers immediately move the timeline playback position to a new location.