SolvingMode

  • The DEFAULT_SOLVE mode solves the model, while other modes focus on validation or error detection.

  • VALIDATE_ONLY mode checks the model's validity and returns as many errors as possible, without solving the model.

  • DETECT_SOME_INFEASIBLE_SHIPMENTS mode only detects and reports infeasible shipments during preprocessing and does not solve the rest of the request.

  • All modes except VALIDATE_ONLY will return an INVALID_REQUEST error if the request is invalid, you can use maxValidationErrors to limit the amount of errors returned.

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.
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.