> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mile.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Dropped Visit

> Why a visit could not be routed, and how to fix it.

**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.

> [!NOTE]
>
> Required permission:
>
> * View result
> * Edit result (move a dropped visit to a vehicle)

![Dropped visits](https://mintcdn.com/mileapp-e5b5ea5a/Z6-EpYCo9EeJaKM6/images/v4/planning/result-dropped.png?fit=max\&auto=format\&n=Z6-EpYCo9EeJaKM6\&q=85\&s=13af90a7b0d02a8bb554d9bd6015cf96)

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

| Reason | How to fix it |
| - | - |
| **Location could not be reached. Check the visit address or map pin.** | There is no road to the visit's location. Check the visit address and move the map pin to a place on a road. |
| **Assigned vehicle not found. Assign an available vehicle or remove the vehicle assignment.** | The visit is assigned to a vehicle that is not in the routing. Add that vehicle, or clear the assignment on the visit. |
| **No matching vehicle tag found. Check the visit tag and vehicle tag.** | No vehicle has all the tags the visit needs. Give at least one vehicle the visit's tags, add a vehicle that has them, or change the visit's tags. |
| **Vehicle capacity exceeded (*capacity*). Add another vehicle or adjust capacity.** | The visit needs more than a vehicle can carry, or no trip had room left. The text shows the capacity involved, such as *weight*. Use a bigger vehicle, turn on [Auto Split](https://docs.mile.app/pages/planning/routing/configuration/auto-split.md), or add capacity or vehicles. |
| **Visit time window is outside every vehicle's working hours. Adjust the visit time window or vehicle working hours.** | The visit's open time does not overlap any vehicle's working time. Change the visit's time window or the vehicles' working hours. |
| **Visit cannot be reached within its time window or working hours. Widen the time window or check the visit location.** | The visit cannot be reached in time even on an empty route. Widen its time window or check its location. |
| **No vehicle has enough working time. Extend working hours or add another vehicle.** | The visit is possible, but the vehicles' working time is already full. Add working hours or vehicles. |

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](https://docs.mile.app/pages/planning/routing/result/editing.md#moving-a-visit)).

## Avoiding dropped visits

1. **Check the coordinates**: make sure every visit has a valid location (a green pin on the [Visit](https://docs.mile.app/pages/planning/routing/visit.md#location-pin) 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.