v7.11 - Live Segment "Approaching" Distance Increasing & Segment Name Issue

I navigated a course (running) that was created in Strava that contained a couple segments. The graphic below shows the course in red, first segment in green and second segment in blue. The second graphic shows the start/stop of the two segments. I would estimate that the end of segment 1 is 30yds from the start of segment 2.

Problem 1:

After I completed segment 1, the watch displayed the normal "Approaching" distance to the start of segment 2. Only the Live segment never started and Approaching distance started to increase as I ran away from the start of the segment. Segment 2 is an out and back (cul-de-sac) about half a mile total. As I returned back to the start of segment 2, the Approaching distance decreased until I reached the segment start location then began to increase again once I passed the segment start. The value continued to increase for the remainder of the run. I would have expected an "Off Segment" alert; cancelling the Live Segment function.

Problem 2:

The segment name was incorrectly (watch screenshot below)

0 nord0296 over 2 years ago

I haven't tried with multiple segments starting close together (but going in different directions), but I notice the Approaching can be a bit "dumb" as well...

In my case I often run a path that has a segment going in the opposite direction than I am running. Somewhere after I pass the start (going in the opposite direction) I get a notice that I am approaching the segment. It's annoying since I am running the opposite direction and have no intention of running the segment.

Secondly, I am often watching a data field screen that is not the first data field screen while I run. It seems when the segment alerts (or maybe it's the whole segment) logic kicks in, I almost sure I end up getting kicked back to the first data screen. It's also annoying and should "return" to the data screen I was on before the segment logic kicked in... but it doesn't. I sometimes run cancelling a segment vs running the segment, so I am sorry that I can't trace it to a use case of cancelled segment vs completed segment - maybe both do it.

0 Dan.Boilermaker over 2 years ago in reply to nord0296

nord0296 said:
It's annoying since I am running the opposite direction and have no intention of running the segment.

I've seen this also when I'm on a "free" run (not navigating). Those and the alerts of upcoming Segments that are 90° to my path don't bother me too much since I will get the Off Segment notice. In the example above, I'm navigating a Strava created course with the segments embedded in the course. To me, that situation sets up deterministic segment locations and should be easier to manage the Live Segment function.

nord0296 said:
I am often watching a data field screen that is not the first data field screen while I run. It seems when the segment alerts (or maybe it's the whole segment) logic kicks in, I almost sure I end up getting kicked back to the first data screen.

I'm pretty sure this happens to me also.