Hi
I have picked up a UR where Waze has routed a user down a restricted road. I can’t see what would cause this. 
Can anyone see what is wrong?
I can’t see which vehicles have been restricted but check that to start with. Sometimes I’ve found restrictions that have been set the wrong way round - allowing restricted and restricting allowed.
Vehicle restriction settings look OK to me (MK, remember that practice mode can be put to good use in cases like this, allowing you read-only access to stuff that WME would otherwise hide when its outside your own editing areas - mine don’t cover this part of the UK either…), and asking livemap for routes around here shows the restriction is being honoured at the moment.
From the partial route trace attached to the UR it also looks like the user was heading to a destination somewhere other than on the restricted road itself, so there’s no reason for Waze to have needed to have sent them that way unless the traffic conditions at the time of their journey were really screwed up.
However, this reminds me that a few weeks ago Waze tried to route me the wrong way up a one-way street, despite there being ample alternative routes available to get me to my chosen destination. So maybe the routing server just gets a bit glitchy from time to time and starts throwing out routes that ignore any restrictions present?
I’m seeing this more often that should be the case. We know the app has limited routing capabilities which seem to kick in occasionally, possibly when the app can’t communicate with the routing server adequately. This capability allows it to direct the user, but it doesn’t seem to have access to restrictions or turn prohibitions, which means routes are often invalid, such as in this example.
Quite where the boundary is between the app telling the user that it can’t access the routing server and providing the route itself has not, as far as I know, ever been discussed. A useful question to ask at the forthcoming UK Conference?