Tread Changes Exisiting Routes - Shaping Point Issues

[proofresistant]

@jfheath
while I'm still with you, the zumo XT2 also recalculates a route and, sometimes, although it's not usually really noticeable, shifts the shaping, a little, also.
I think that's the reason why my tests with my “WK 3B...” route result in seemingly endless synchronizations. First, the tread app does what it thinks, then the navigation device does what it thinks, then the tread app does what it thinks again, and so on, endless I suspect. But this doesn't happen with every shaped route.

[proofresistant]

... the zumo XT2 also recalculates a route and, sometimes, although it's not usually really noticeable, shifts the shaping, a little, also. ...

Just a few minutes after writing that, I looked at my Navi Tread app setup again.
And lo and behold, I have to significantly revise my statement from earlier.
It also happens that the shift is clearly visible with significant effects, without anything landing in the cloud.

Calculation (manipulation) of the route in the Tread app is not possible, as a message appears for a fraction of a second, roughly translated as “Route cannot be calculated, no or poor internet connection.”

Ergo, in this case, without my manual intervention and without any message, the navigation device must have been the cause.