Known issues

This list shows the known issues in the HERE Routing API v8.

When an avoid option would make the route significantly longer in travel time, the API may not return a route that respects that option, even if an alternative route exists.
In areas with ferry connections, the API may select a different ferry than expected, or calculate an overland route instead.
The API doesn't support time restrictions for smart interchanges in Japan. As a result, routes may pass through smart interchanges that are inaccessible at the departure time.
If an avoid[areas] polygon is too large to be fully avoided, the calculated route may take a suboptimal path through part of the avoided area.
If the driver[schedule] configuration produces a driving segment shorter than 241 seconds (either between stops or at the start of the route), the route calculation fails.
Avoiding highways or toll roads on very long truck routes may result in slow response times or no route being returned.
The routeLabels response schema (returned when using return=routeLabels) doesn't use camelCase, which does not conform to HERE API standards.

Related content