@Doug-Robinson The problem indeed is that a track does not have these avoid options so when the app "returns to track" after you missed a part, it really just sends you most efficiently back to the track.
If the issue where losing the original track entirely is solved correctly you wouldn't want these avoid options anyway. They now only become very apparent because you are sometimes sent to the destination directly 😉
We'll aim at fixing that!