Reference documentation and code samples for the Google Cloud Optimization V1 Client class 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.
This should never be used. If we are unable to understand why a
shipment was skipped, we simply return an empty set of reasons.
Generated from protobuf enumCODE_UNSPECIFIED = 0;
NO_VEHICLE
Value: 1
There is no vehicle in the model making all shipments infeasible.
Generated from protobuf enumNO_VEHICLE = 1;
DEMAND_EXCEEDS_VEHICLE_CAPACITY
Value: 2
The demand of the shipment exceeds a vehicle's capacity for some
capacity types, one of which isexample_exceeded_capacity_type.
Generated from protobuf enumDEMAND_EXCEEDS_VEHICLE_CAPACITY = 2;
CANNOT_BE_PERFORMED_WITHIN_VEHICLE_DISTANCE_LIMIT
Value: 3
The minimum distance necessary to perform this shipment, i.e. from
the vehicle'sstart_locationto the shipment's pickup and/or delivery
locations and to the vehicle's end location exceeds the vehicle'sroute_distance_limit.
Note that for this computation we use the geodesic distances.
Generated from protobuf enumCANNOT_BE_PERFORMED_WITHIN_VEHICLE_DISTANCE_LIMIT = 3;
CANNOT_BE_PERFORMED_WITHIN_VEHICLE_DURATION_LIMIT
Value: 4
The minimum time necessary to perform this shipment, including travel
time, wait time and service time exceeds the vehicle'sroute_duration_limit.
Note: travel time is computed in the best-case scenario, namely as
geodesic distance x 36 m/s (roughly 130 km/hour).
Generated from protobuf enumCANNOT_BE_PERFORMED_WITHIN_VEHICLE_DURATION_LIMIT = 4;
Same as above but we only compare minimum travel time and the
vehicle'stravel_duration_limit.
Generated from protobuf enumCANNOT_BE_PERFORMED_WITHIN_VEHICLE_TRAVEL_DURATION_LIMIT = 5;
CANNOT_BE_PERFORMED_WITHIN_VEHICLE_TIME_WINDOWS
Value: 6
The vehicle cannot perform this shipment in the best-case scenario
(seeCANNOT_BE_PERFORMED_WITHIN_VEHICLE_DURATION_LIMITfor time
computation) if it starts at its earliest start time: the total time
would make the vehicle end after its latest end time.
Generated from protobuf enumCANNOT_BE_PERFORMED_WITHIN_VEHICLE_TIME_WINDOWS = 6;
VEHICLE_NOT_ALLOWED
Value: 7
Theallowed_vehicle_indicesfield of the shipment is not empty and
this vehicle does not belong to it.
Generated from protobuf enumVEHICLE_NOT_ALLOWED = 7;
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Google Cloud Optimization V1 Client - Class Code (1.0.5)\n\nVersion latestkeyboard_arrow_down\n\n- [1.0.5 (latest)](/php/docs/reference/cloud-optimization/latest/V1.SkippedShipment.Reason.Code)\n- [1.0.4](/php/docs/reference/cloud-optimization/1.0.4/V1.SkippedShipment.Reason.Code)\n- [0.7.0](/php/docs/reference/cloud-optimization/0.7.0/V1.SkippedShipment.Reason.Code)\n- [0.6.5](/php/docs/reference/cloud-optimization/0.6.5/V1.SkippedShipment.Reason.Code)\n- [0.5.1](/php/docs/reference/cloud-optimization/0.5.1/V1.SkippedShipment.Reason.Code)\n- [0.4.0](/php/docs/reference/cloud-optimization/0.4.0/V1.SkippedShipment.Reason.Code)\n- [0.3.4](/php/docs/reference/cloud-optimization/0.3.4/V1.SkippedShipment.Reason.Code)\n- [0.2.0](/php/docs/reference/cloud-optimization/0.2.0/V1.SkippedShipment.Reason.Code)\n- [0.1.9](/php/docs/reference/cloud-optimization/0.1.9/V1.SkippedShipment.Reason.Code) \nReference documentation and code samples for the Google Cloud Optimization V1 Client class Code.\n\nCode identifying the reason type. The order here is meaningless. In\nparticular, it gives no indication of whether a given reason will\nappear before another in the solution, if both apply.\n\nProtobuf type `google.cloud.optimization.v1.SkippedShipment.Reason.Code`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Optimization \\\\ V1 \\\\ SkippedShipment \\\\ Reason\n\nMethods\n-------\n\n### static::name\n\n### static::value\n\nConstants\n---------\n\n### CODE_UNSPECIFIED\n\n Value: 0\n\nThis should never be used. If we are unable to understand why a\nshipment was skipped, we simply return an empty set of reasons.\n\nGenerated from protobuf enum `CODE_UNSPECIFIED = 0;`\n\n### NO_VEHICLE\n\n Value: 1\n\nThere is no vehicle in the model making all shipments infeasible.\n\nGenerated from protobuf enum `NO_VEHICLE = 1;`\n\n### DEMAND_EXCEEDS_VEHICLE_CAPACITY\n\n Value: 2\n\nThe demand of the shipment exceeds a vehicle's capacity for some\ncapacity types, one of which is `example_exceeded_capacity_type`.\n\nGenerated from protobuf enum `DEMAND_EXCEEDS_VEHICLE_CAPACITY = 2;`\n\n### CANNOT_BE_PERFORMED_WITHIN_VEHICLE_DISTANCE_LIMIT\n\n Value: 3\n\nThe minimum distance necessary to perform this shipment, i.e. from\nthe vehicle's `start_location` to the shipment's pickup and/or delivery\nlocations and to the vehicle's end location exceeds the vehicle's\n`route_distance_limit`.\n\nNote that for this computation we use the geodesic distances.\n\nGenerated from protobuf enum `CANNOT_BE_PERFORMED_WITHIN_VEHICLE_DISTANCE_LIMIT = 3;`\n\n### CANNOT_BE_PERFORMED_WITHIN_VEHICLE_DURATION_LIMIT\n\n Value: 4\n\nThe minimum time necessary to perform this shipment, including travel\ntime, wait time and service time exceeds the vehicle's\n`route_duration_limit`.\n\nNote: travel time is computed in the best-case scenario, namely as\ngeodesic distance x 36 m/s (roughly 130 km/hour).\n\nGenerated from protobuf enum `CANNOT_BE_PERFORMED_WITHIN_VEHICLE_DURATION_LIMIT = 4;`\n\n### CANNOT_BE_PERFORMED_WITHIN_VEHICLE_TRAVEL_DURATION_LIMIT\n\n Value: 5\n\nSame as above but we only compare minimum travel time and the\nvehicle's `travel_duration_limit`.\n\nGenerated from protobuf enum `CANNOT_BE_PERFORMED_WITHIN_VEHICLE_TRAVEL_DURATION_LIMIT = 5;`\n\n### CANNOT_BE_PERFORMED_WITHIN_VEHICLE_TIME_WINDOWS\n\n Value: 6\n\nThe vehicle cannot perform this shipment in the best-case scenario\n(see `CANNOT_BE_PERFORMED_WITHIN_VEHICLE_DURATION_LIMIT` for time\ncomputation) if it starts at its earliest start time: the total time\nwould make the vehicle end after its latest end time.\n\nGenerated from protobuf enum `CANNOT_BE_PERFORMED_WITHIN_VEHICLE_TIME_WINDOWS = 6;`\n\n### VEHICLE_NOT_ALLOWED\n\n Value: 7\n\nThe `allowed_vehicle_indices` field of the shipment is not empty and\nthis vehicle does not belong to it.\n\nGenerated from protobuf enum `VEHICLE_NOT_ALLOWED = 7;`"]]