Code identifying the reason type. The order here is meaningless. In
particular, it gives no indication of whether a given reason will
appear before another in the solution, if both apply.
The minimum distance necessary to perform this shipment, i.e. from
the vehicle's start_location to the shipment's pickup and/or delivery
locations and to the vehicle's end location exceeds the vehicle's
route_distance_limit.
Note that for this computation we use the geodesic distances.
CannotBePerformedWithinVehicleDurationLimit
The minimum time necessary to perform this shipment, including travel
time, wait time and service time exceeds the vehicle's
route_duration_limit.
Note: travel time is computed in the best-case scenario, namely as
geodesic distance x 36 m/s (roughly 130 km/hour).
CannotBePerformedWithinVehicleTimeWindows
The vehicle cannot perform this shipment in the best-case scenario
(see CANNOT_BE_PERFORMED_WITHIN_VEHICLE_DURATION_LIMIT for time
computation) if it starts at its earliest start time: the total time
would make the vehicle end after its latest end time.
CannotBePerformedWithinVehicleTravelDurationLimit
Same as above but we only compare minimum travel time and the
vehicle's travel_duration_limit.
DemandExceedsVehicleCapacity
The demand of the shipment exceeds a vehicle's capacity for some
capacity types, one of which is example_exceeded_capacity_type.
NoVehicle
There is no vehicle in the model making all shipments infeasible.
Unspecified
This should never be used. If we are unable to understand why a
shipment was skipped, we simply return an empty set of reasons.
VehicleNotAllowed
The allowed_vehicle_indices field of the shipment is not empty and
this vehicle does not belong to it.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["The document provides a list of `Code` enums within the `Google.Cloud.Optimization.V1.SkippedShipment.Types.Reason.Types` namespace, detailing the reasons why a shipment might be skipped in the Google Cloud Optimization service."],["The latest version of the documentation is 2.6.0, with previous versions ranging from 2.5.0 back to 1.0.0-beta01, all describing the `Code` enum."],["The `Code` enum contains fields like `CannotBePerformedWithinVehicleDistanceLimit`, `DemandExceedsVehicleCapacity`, and `NoVehicle`, each with a specific description explaining the reason for a shipment being skipped, and there are also versions of the fields that pertain to time limits instead of distance limits."],["The `Unspecified` field within the `Code` enum is designated for cases where the reason for a shipment's omission cannot be determined, and is not meant to be used otherwise."],["The enum can be found in the `Google.Cloud.Optimization.V1.dll` assembly."]]],[]]
