Page 1 of 1

The request is not allowed to contain routes

Posted: Mon Dec 08, 2025 7:18 am
by martinelsner
Hi,

while trying to exchange xServer by Developer at one of our customers, I have to implement the following requirement:
calculate the times and distances again for an existing tour, respecting the time slots for all locations.
So I call the Optiflow API with the same data as for the initial optimization, but pass the current sequence as route. To achieve that Optiflow doesn't change the sequence, I use the respectedSequences and suitable categories in the tasks.

I then get the following result:
{
"traceId": "prod_e8dd70d1577dce418fa28e746ac3dff9",
"description": "A product-specific restriction is exceeded.",
"errorCode": "ROUTE_OPTIMIZATION_RESTRICTION_EXCEEDED",
"causes": [
{
"description": "The request is not allowed to contain routes.",
"errorCode": "ROUTE_OPTIMIZATION_ROUTES_FORBIDDEN",
"parameter": "$.routes",
"details": {}
}
],
"details": {}
}

Is this a problem with the current plan assigned to this customer, or is it caused by the data we passed to the service?

Re: The request is not allowed to contain routes

Posted: Mon Dec 08, 2025 7:49 am
by Joost
it is caused by your plan. The standard plans do not allow for routes as a input parameter. Please contact your sales representative. They can inform you about the license implications of using routes and if need be provide you with a test license that does allow routes.