I just spent some time debugging this, and was finally able to find a solution. Am wondering if there is a better way.
It seems that the OnRouteFinished() callback, isn’t a sign that you are free to send the seeker on a new StartPath() right away. I was wondering why it wasn’t working, when I noticed that it was making the call for the next route, even though the seeker hadn’t completely stopped moving.
This made me think to use a coroutine, with a delay, before making the next call, which fixed the issue. Is there a parameter we can pass to StartPath, where it only calls OnRouteFinished(), when we are clear to start the next path? Thanks.