Frequently asked questions

To view the source task data, use a link in the following format: https://courier.yandex.ru/vrs/api/v1/log/request/<task_id>, where

task_id is the ID of the solved task.

That depends on how you run the planning task. If you run the planning task:

• Via the API — Process the addresses in Geocoder first.

• In the interface — The built-in geocoder automatically processes the addresses (to learn more, see the Map subsection in Import window).

Yes, there is. By default, you can ran no more than 10 parallel planning tasks with a single access key.

You can view the standard planning time for the Optimal setting in Request processing time. If you need to set further limits, contact support.

No, you don't. Your task is saved under a unique number that you can find in the browser address bar: https://yandex.ru/courier/companies/<company_id>/depots/all/mvrp/<task_id>, where task_id is the ID of the solved task, and company_id is the ID of the company.

To receive the solution, refresh the page where you started the task.

There are two types of limits In the Planning service:

• By the number of requests per day. If this limit is exceeded, you'll get a "Counter tasks_total_solved limit exceeded" error.

• By the number of simultaneously processed requests (for example, planning for different cities or depots). If this limit is exceeded, you'll get a "Quota limit exceeded" error.

To increase these quotas, contact your manager or support.

If your business requires running a large number of tasks simultaneously, organize a queue to send a new planning request only after receiving a response to the previous one. See Obtaining results. Estimate the time to process the request.

The Excel file doesn't support some of the parameters yet.

To learn more, follow the links:

• Parameters available via Excel

• Parameters available via the API

Use the Grouped routes option.

Increase the cost.km cost (see Vehicle or courier cost). If you use hard order or shift time windows, try making them soft.

There are several reasons for that. Most often, it's because of the hard restrictions that the algorithm can't violate.

• A shift, depot, or order hard time window.

• Order and vehicle compatibility.

In some scenarios, this is expected. See Planning orders that can be rescheduled / Planning part of the orders.

To find out the reasons, check out the conditions of the task:

1. Check the order's penalty.drop value: it shouldn't be too small or set to 0.

2. Make all order time windows soft.

3. Remove order tags.

4. Remove the order load_types.

See Multiple time windows in the order.

To learn about reasons for long waiting times and how to minimize them, see Minimizing waiting time for couriers.

This way, when orders are combined into multi-orders, the parking time is counted only once, and the handover time is counted based on the number of orders.

Use the Vehicle tags function.

Use the Order incompatibility function.

The courier workload settings are described in the Planning the loading of your own couriers case.

The courier workload settings are described in the Minimizing the number of couriers case.

No. Within one planning task, you can select only one transportation method for a courier.

A special case is planning tasks in transit mode. Here, the courier uses public transport, gets off, and walks to the delivery point.

In each planning task, specify the couriers' working hours on a specific day. If the schedules are different on different days, indicate that when creating the API request or preparing the data in Excel.

If you know the orders and courier working hours for the next days, use the Planning orders for multiple days case.

Enable flexible start time.

Add a garage point and specify its ID in the vehicle.finish_at field. The route will end at the specified location.

If you enable returning to the depot at the end of the shift (vehicle.return_to_depot = TRUE), the courier first returns to the depot and then goes to the finish_at point.

To learn more, see Returning to a depot at the end of the working day and Start or end of the route at an arbitrary point.

Increase the handling time. It may be too "optimistic". You can also use the Limit the number of stops per shift option.

Reduce the cost of using your own vehicles. To learn more, see the Using your own and hired transport at the same time scenario.

Penalties are used to configure the algorithm. They aren't related to the way you evaluate the cost of logistics.

For recommendations on using penalties, see the logistics scenarios.

The total solution cost is calculated by summing the individual route costs with penalties and adding any penalties for violating routing options. For more information, see Cost with penalties.

To learn more, see Running the API and editing the solution in the interface.

There are two options:

• In the Routing workspace. This option supports editing routes and saving the results. To learn more, see Editing a solution.

• At https://courier.yandex.ru/mvrp-map#<task_id>, where task_id is the ID of the resulting solution. You can only view the solution with this option, but you can't edit it.