- The API did not change.
- A
removalStrategyconstraint takes its unloading order in thestrategyfield. The reference called this fieldremovalStrategyuntil this fix. - The API ignores a field it doesn’t know. A constraint written with
"removalStrategy": "lifo"was still accepted, and it appliedlifo, becauselifois the default. Rename the field tostrategyin your payloads anyway, so that the order you set is the one the API reads. - A
RemovalStrategyViolationreturns the order instrategytoo. The reference called itremovalStrategyType. See Last in, first out.
Released on 2026-10-20. A cost cap needs a maximum, and a tag that matches no resource raises a warning
- A
maxCumulatedCostentry inglobalConstraintswithoutmaximumis now rejected with a400INVALID_VALUEerror. Before, the API accepted it and stored amaximumof 0, so the cap allowed no counted cost at all. Addmaximumto any such entry before you send the plan again. - A tag in the
costsByResourceTagof amaxCumulatedCostentry that no resource of the plan carries now raises a warning in the response. The plan is still accepted, and the tag still counts nothing. - See Capping a fleet-wide cost with
maxCumulatedCost.
- The API did not change.
height,width, andlengthof atruckprofile have always been whole numbers of centimetres. The reference said metres until this fix.- A whole number in metres, such as
length: 12, is accepted with no error and read as 12 centimetres. Check any truck profile that you wrote from the old reference. See Data model.
- A cost whose base is 0 on a tour is now 0. Before, a resource that was used paid the
constantCostof that cost even then. - This affects
costsByStopTagon a tour that visits no stop with the tag, andcostsByCapacityon a tour that handles none of that capacity. The same rule holds for every cost built fromconstantCost,costCoeff, andovercostCoeff. - Two cases never paid and still do not: a resource that is not used, and a tag that no stop of the plan carries.
- If a minimum must hold on every tour, put it in
using, becauseusingis charged once for every resource that is used. See Piecewise-linear cost functions and Guaranteeing a minimum per-tour revenue.
GET /plans(light representation) is now always paginated — previously, no paging was applied unlesspageoritemsPerPagewas explicitly set.PUT /plans/{planId}/runningnow returns anEnvelopedPlanReferencebody instead of an empty response.- The light plan representation gains the same metadata fields as the full
Planobject:state,nbResources,nbOrders,createdAt,createdBy,updatedAt,updatedBy,archivedAt. - Several plan and paging fields that were
nullablenow use field absence instead — check for the field’s presence rather than for anullvalue. - New
Warningconcept: non-blocking amendments applied to an accepted payload (traffic turned off, crow-fly forced,maxOptimizationDurationclamped, and so on) are now surfaced on five response envelopes instead of silently applied.

