Reference documentation and code samples for the Cloud Optimization v1 API enum OptimizeToursRequest.Types.SolvingMode.
Defines how the solver should handle the request. In all modes but
VALIDATE_ONLY, if the request is invalid, you will receive an
INVALID_REQUEST error. See
[max_validation_errors][google.cloud.optimization.v1.OptimizeToursRequest.max_validation_errors]
to cap the number of errors returned.
Only populates
[OptimizeToursResponse.validation_errors][google.cloud.optimization.v1.OptimizeToursResponse.validation_errors]
or
[OptimizeToursResponse.skipped_shipments][google.cloud.optimization.v1.OptimizeToursResponse.skipped_shipments],
and doesn't actually solve the rest of the request (status and routes
are unset in the response).
If infeasibilities in injected_solution_constraint routes are detected
they are populated in the
[OptimizeToursResponse.validation_errors][google.cloud.optimization.v1.OptimizeToursResponse.validation_errors]
field and
[OptimizeToursResponse.skipped_shipments][google.cloud.optimization.v1.OptimizeToursResponse.skipped_shipments]
is left empty.
IMPORTANT: not all infeasible shipments are returned here, but only the
ones that are detected as infeasible during preprocessing.
ValidateOnly
Only validates the model without solving it: populates as many
[OptimizeToursResponse.validation_errors][google.cloud.optimization.v1.OptimizeToursResponse.validation_errors]
as possible.
[[["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-08-07 UTC."],[[["\u003cp\u003eThis document provides reference documentation for the \u003ccode\u003eOptimizeToursRequest.Types.SolvingMode\u003c/code\u003e enum within the Google Cloud Optimization v1 API, outlining different modes for handling optimization requests.\u003c/p\u003e\n"],["\u003cp\u003eThe latest version of the API for this enum is 2.6.0, with documentation available for versions ranging from 1.0.0-beta01 to 2.6.0, each link directing to their respective content.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eSolvingMode\u003c/code\u003e enum defines how the solver manages requests, including \u003ccode\u003eDefaultSolve\u003c/code\u003e for solving the model, \u003ccode\u003eDetectSomeInfeasibleShipments\u003c/code\u003e for identifying infeasible shipments during preprocessing, and \u003ccode\u003eValidateOnly\u003c/code\u003e for validating the model without solving it.\u003c/p\u003e\n"],["\u003cp\u003eIn most solving modes, the API will return an \u003ccode\u003eINVALID_REQUEST\u003c/code\u003e error if there is an invalid request, however, the number of errors returned can be capped by the user with \u003ccode\u003emax_validation_errors\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eIt is worth noting that when using \u003ccode\u003eDetectSomeInfeasibleShipments\u003c/code\u003e only some infeasible shipments are returned, as opposed to all of them.\u003c/p\u003e\n"]]],[],null,[]]
