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 maxValidationErrors to cap the number of errors returned.

Enums
DEFAULT_SOLVE	Solve the model. Warnings may be issued in [OptimizeToursResponse.validation_errors][google.cloud.optimization.v1.OptimizeToursResponse.validation_errors].
VALIDATE_ONLY	Only validates the model without solving it: populates as many OptimizeToursResponse.validation_errors as possible.
DETECT_SOME_INFEASIBLE_SHIPMENTS	Only populates OptimizeToursResponse.validation_errors or OptimizeToursResponse.skipped_shipments, and doesn't actually solve the rest of the request (status and routes are unset in the response). If infeasibilities in injectedSolutionConstraint routes are detected they are populated in the OptimizeToursResponse.validation_errors field and 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.
TRANSFORM_AND_RETURN_REQUEST	This mode only works if ShipmentModel.objectives is not empty. The request is not solved. It is only validated and filled with costs corresponding to the given objectives. Also see the documentation of ShipmentModel.objectives. The resulting request is returned as OptimizeToursResponse.processed_request. Experimental: See https://developers.google.com/maps/tt/route-optimization/experimental/objectives/make-request for more details.