Bing Maps REST returning bad directions when passing waypoints

I'm working on an Android app that utilizes BING maps and their directions REST service. I allow the user to input origin, destination, and avoid types (i.e. avoid highways, tolls, etc...) to obtain directions. After BING returns the directions I display them on a BING map and then allow the user to save the directions. I save each waypoint that is involved. The user later can display their saved directions back on a BING map. At this point I pass each waypoint to BING to get the directions. As you can see in the screen shots below, the first directions are created with just an Origin and Destination (and avoid types), and th开发者_运维技巧e second one is purely created on passing each waypoint that was saved.

I've confirmed that the waypoints that come back from the initial request are the exact same as the waypoints I'm saving and passing back to BING.

Here are some live queries that I used for the screens below:

My generated link to BING REST

Query with each waypoint

Any ideas as to what is going on or what I can do to fix this? It's like BING wants to further optimize the route, but ends up making it worse. In the second picture you can see it has you get off the freeway, then back on, then get off again and then back track to where you just got off.

Good Route with initial input with Origin and Destination:

Bad Route being obtained with saved waypoints:

---

Sounds like it might be a problem with the bing library. Have you tried filling a bug report with them?