Hi @Mike-wiruth unfortunately its not something that I see as within MRA's control
The surface condition on a road/track is part of the map data which is supplied the exterior map data suppliers, Here, TomTom & OpenStreetMap, all MRA can do is plot a route relying on that data
I can tell you now that the Here data, which is what MRA use for their navigation app, is by far the worst for routing down unpaved tracks, taking shortcuts where roads don't even exisit, even when there are perfectly good roads that are just a little bit longer/slower nearby.
The only way I think you can reduce the chance of such surprises is by switching between the routing profiles/& the overlay maps, & by comparing the different paths each profile generates
I find very often the Here routing profile will route down a path, which when inspected by viewing the OSM overlay map, it turns out to be designated as a track & not a road at all
If your using an XT as suggested by your signature that will introduce a whole level of other surprises, I found after 2 years of meticulously careful planning could I prevent it from doing something completely unexpected