Yes, this was the fault, no I get debug info in the log file:
Debug: Opening ride: "2025_12_01_11_29_29.json" for "Golden_C_Sprint Unterpremstätten"
Debug: Start point identified...
Debug: Start time 2552 M
Debug: WARNING route diverge at 2555 ( 2555 ) after 3 secs for 0.1126 km 46.9688 - 15.4054 / 46.9685 - 15.404 M
Debug: WARNING route diverge at 2556 ( 2556 ) after 4 secs for 0.120537 km 46.9688 - 15.4054 / 46.9685 - 15.4039 M
Debug: WARNING route diverge at 2566 ( 2566 ) after 14 secs for 0.124231 km 46.9688 - 15.4054 / 46.9684 - 15.4039 M
Debug: STOP route diverge at 2566 ( 2566 ) after 14 secs for 0.124231 km 46.9688 - 15.4054 /
My interpretation: GC see I passed the starting point but then i went some were but not on the segment.
This picture shows the segment: it starts right after the western roundabout:
At my recent ride I came from the eastern roundabout went around the western into the segment, GC found the starting point on the way to the western roundabout, and stopped because of the wrong direction, GC did not find the starting point on my way on the segment again.....
Same on today's ride were I went again from east to west and then on the segment form west to east...
Any chance to let GC even in situations like this recognize the segment?
(for sure I can provide all the files - just instruct me how to export correct)
Cheers,
Helmut