Skip to main content
Dropped visits are visits the optimization could not put on any vehicle. In the List view, click Dropped under the vehicles to see them as Dropped visits (n). The result card also shows the count, for example Dropped 2/20, and the map shows dropped visits as red pins.
Required permission:
  • View result
  • Edit result (move a dropped visit to a vehicle)
Dropped visits
Each dropped visit shows its tags, address, times, capacity and a Reason, for example Reason: No matching vehicle tag found. Check the visit tag and vehicle tag. The reason is written in your language. If your user has no language set, it uses the organization language, and English when that is not available either. The language is decided when the routing runs. Results created earlier may show the message as it was stored at that time.

Why a visit is dropped

When the visit belongs to a visit group, the reason names the real cause for the visit, such as capacity or time. Results made before this change can also show Visit Group ‘group’ exceeds vehicle limits. Reduce visits, adjust vehicle settings, or split the group. To fix it, reduce the visits in the group, change the vehicle settings, or split the group.

Next steps

After fixing the data, optimize again. Or move the dropped visit to a suitable vehicle by hand with Move visit (see Editing).

Avoiding dropped visits

  1. Check the coordinates: make sure every visit has a valid location (a green pin on the Visit page).
  2. Balance capacity: match what the visits need with what the vehicles can carry.
  3. Line up times: make sure the visits’ open times fit the vehicles’ working times.
  4. Keep tags consistent: tag visits and vehicles the same way.