Known issues and workarounds

The following list contains known issues in the current release.

• In some extreme cases, a route respecting an avoid option might not be returned even if there is another option. This happens mainly when avoiding the specific attribute would make the route extraordinarily long compared to the route without the avoid option, especially in terms of time.
• Routes in areas with possible ferry connections may differ from customer's specific expectations in some cases. For example, a different ferry connection may be used, or an overland route may be calculated.
• Time restrictions for smart interchanges in Japan are not considered. This may lead to routes going through smart interchanges that are not accessible at this time of day.
• If a large area is provided for avoid[areas] and it could not be avoided, the calculated route may have a suboptimal path inside the avoided area.
• If the driving and rest time schedule in driver[schedule] would result in a driving time between stops, or at the start, of less than 241 seconds, the route calculation will fail.
• Avoiding highways and/or toll roads for very long truck routes can result in slow responses, or a route not being returned at all.
• The routeLabels response schema (requested with return=routeLabels) is not camelCase, which does not conform to HERE API standards.