Why a trip stayed unassigned

The reasons the optimizer leaves a trip in the backlog, and what to do about each.

Written for
Dispatchers
Reading time
1 min
Last reviewed
August 3, 2026

An unassigned trip after a scheduling run is not a failure — it is the optimizer declining to break a hard constraint. Each one carries a reason.

ReasonWhat it meansWhat to do
No capable vehicle availableEvery vehicle that can serve this service type is already committed during the windowActivate another suitable vehicle, or widen the pickup window if the rider can flex
No vehicle with this capabilityNo active vehicle in the fleet is flagged for the required service type at allCheck the capability flags on your fleet before assuming you are short of vehicles
Window cannot be metTravel time from any feasible predecessor exceeds the windowConfirm the addresses geocoded correctly; a bad geocode produces impossible travel times
Missing pickup timeThe trip has no anchor on the timelineSet a time, or mark it will-call if the time genuinely is not known
Driver hours exceededPlacing it would break a shift limitAdd coverage, or move the trip to a different part of the day

Related

Still stuck?

Technical documentation

API references, data model, webhook payloads and integration guides — the detail behind the workflows described here. Available to signed-in Naveera customers.

Open documentation

Ask your team

Support requests are raised from inside Naveera Console, where your organization and your role are already known — which means the answer can be about your configuration rather than the general case.

Settings → Support, or ask your organization’s administrator