Reference documentation and code samples for the Cloud Optimization v1 API enum SkippedShipment.Types.Reason.Types.Code.
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."],[[["\u003cp\u003eThis page provides documentation for the \u003ccode\u003eSkippedShipment.Types.Reason.Types.Code\u003c/code\u003e enum within the Google Cloud Optimization v1 API, detailing reasons why a shipment might be skipped.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation is for version 2.0.0 of the API, and provides links to other versions, with version 2.6.0 being the latest.\u003c/p\u003e\n"],["\u003cp\u003eThe enum \u003ccode\u003eCode\u003c/code\u003e defines various reasons for skipped shipments, such as \u003ccode\u003eCannotBePerformedWithinVehicleDistanceLimit\u003c/code\u003e, \u003ccode\u003eDemandExceedsVehicleCapacity\u003c/code\u003e, and \u003ccode\u003eNoVehicle\u003c/code\u003e, each with a specific description.\u003c/p\u003e\n"],["\u003cp\u003eThe different reasons for a skipped shipment are associated with constraints related to vehicle capacity, distance, time, or vehicle limitations, as well as a reason for when there are no vehicles at all in the model.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation is located within the \u003ccode\u003eGoogle.Cloud.Optimization.V1\u003c/code\u003e namespace and is contained within the \u003ccode\u003eGoogle.Cloud.Optimization.V1.dll\u003c/code\u003e assembly.\u003c/p\u003e\n"]]],[],null,[]]
