Release notes

This page documents production updates to Cloud Optimization API. Check this page for announcements about new or updated features, bug fixes, known issues, and deprecated functionality.

You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or you can programmatically access release notes in BigQuery.

April 14, 2022


Cloud Fleet Routing is now generally available (GA).

You can now grant access to Cloud Optimization IAM roles to a user, a group, or a service account to perform create or get operations in the context of a batchOptimizeTours request.

You can now create models that can solve up to 120 mns (instead of 60 mns) using automatic checkpoints in a batchOptimizeTour request to solve complex problems.

You can now set a soft_max_load with related costs on your vehicles to balance the load limit across your fleet.

Optimization AI now has a concurrent batch solve quota of 60000 timeout seconds per project.

November 15, 2021


Cloud Fleet Routing is now available in General Availability GA.

You can now use Place ID in Cloud Fleet Routing as an alternative to latitude and longitude, which is still available.

You can now accept Google Map Platform's Terms of Service when using Distance Matrix API in Cloud Fleet Routing through Google Maps for Fleet Routing.

demands[]/capacities[] fields are improved with Load Limit: this feature will help you dynamically control how much shipment load will be added to each vehicle, pushing the solver to balance out the shipments more evenly.

The demands[]/capacities[] related fields will be deprecated on November 15th, 2022.

googleMapsApiKey field in optimizeTours is deprecated and replaced with Google Maps for Fleet Routing. Update your code to remove the google_maps_api_key field from sending requests. If not, it causes errors on the client side.

July 01, 2021


Cloud Optimization AI rolled out updates to replace ShipmentRoute.TravelStep with ShipmentRoute.Transition.

Transitions are meant to inform about everything that is happening before and/or after visits. Whereas a TravelStep only contained travel distance and duration information, a Transition also holds quantity loads and delay durations. More fields will be added to Transitions in the future.

This is a backwards-compatible change: the old fields are kept and maintained. No features or capabilities were removed. Details for this release are listed here:

  • ShipmentRoute.travel_steps is changed to ShipmentRoute.transitions.
  • ShipmentRoute.Visit.delay_before_start and ShipmentRoute.delay_before_vehicle_end are changed to ShipmentRoute.Transition.delay_duration.
  • ShipmentRoute.Visit.arrival_loads and ShipmentRoute.end_loads are changed to ShipmentRoute.Transition.loads.
  • ShipmentRoute.TravelStep.duration is changed to ShipmentRoute.Transition.travel_duration.
  • ShipmentRoute.TravelStep.distance_meters is changed to ShipmentRoute.Transition.travel_distance_meters.