# Route not feasible : why?

**URL:** <https://support.routexl.com/t/route-not-feasible-why/2433>\
**Category:** API\
**Created:** [January 21, 2023, 8:43pm UTC](https://support.routexl.com/t/route-not-feasible-why/2433 "2023-01-21T20:43:47Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![starshipcoder](https://support.routexl.com/letter_avatar_proxy/v4/letter/s/f04885/32.png) [@starshipcoder](https://support.routexl.com/u/starshipcoder)\
**Post date:** [January 21, 2023, 8:43pm UTC](https://support.routexl.com/t/route-not-feasible-why/2433/1 "2023-01-21T20:43:48Z")

</div>

Hi

I sent this route to api:  
[{“address”:“starting”,“lat”:“48.329302”,“lng”:“-0.877466”},{“address”:“1”,“restrictions”:{“ready”:300,“due”:180},“lat”:“48.0600459”,“lng”:“-0.7346208”,“servicetime”:15},{“address”:“2”,“restrictions”:{“ready”:300,“due”:180},“lat”:“47.9294196”,“lng”:“-0.8025222”,“servicetime”:15},{“address”:“3”,“restrictions”:{“ready”:300,“due”:180},“lat”:“47.9294196”,“lng”:“-0.8025222”,“servicetime”:15},{“address”:“4”,“restrictions”:{“ready”:300,“due”:180},“lat”:“47.9294196”,“lng”:“-0.8025222”,“servicetime”:15},{“address”:“5”,“restrictions”:{“ready”:300,“due”:180},“lat”:“48.0567795”,“lng”:“-0.7890905”,“servicetime”:15},{“address”:“6”,“restrictions”:{“ready”:300,“due”:180},“lat”:“48.1777287”,“lng”:“-0.8903828”,“servicetime”:15},{“address”:“7”,“restrictions”:{“ready”:300,“due”:180},“lat”:“48.0983543”,“lng”:“-0.7914522”,“servicetime”:15},{“address”:“8”,“restrictions”:{“ready”:300,“due”:180},“lat”:“48.0722042”,“lng”:“-0.718203”,“servicetime”:15},{“address”:“arrival”,“lat”:“48.329302”,“lng”:“-0.877466”}]

I get this as a response: not feasible.

{id: g05245M2, count: 10, **feasible: false,** route: {0: {name: starting, arrival: 0, distance: 0}, 1: {name: 1, arrival: 21, distance: 20.6}, 2: {name: 8, arrival: 49, distance: 34.1}, 3: {name: 7, arrival: 70, distance: 41.9}, 4: {name: 3, arrival: 88, distance: 44.5}, 5: {name: 2, arrival: 110, distance: 50.5}, 6: {name: 6, arrival: 140, distance: 67}, 7: {name: 5, arrival: 155, distance: 67}, 8: {name: 4, arrival: 170, distance: 67}, 9: {name: arrival, arrival: 229, distance: 120.2}}}

If I delete one step, or add another, it works.

Why ? Is there a problem with my request ?

Regards

---

<div class="post-metadata">

**Author:** ![RouteXL](https://support.routexl.com/user_avatar/support.routexl.com/routexl/32/347_2.png) [@RouteXL](https://support.routexl.com/u/RouteXL)\
**Post date:** [January 22, 2023, 8:51am UTC](https://support.routexl.com/t/route-not-feasible-why/2433/2 "2023-01-22T08:51:14Z")

</div>

The ready and due times are not adding any value here but hamper the feasibility. All stops have a ready time of 300 (05:00) and a due time of 180 (03:00), while the whole route can be done in 229 minutes. Is there any special reason you have these restrictions?

Note: you can import the JSON locations input on the website, and create a route from that, for better understanding of what is happening.

---

<div class="post-metadata">

**Author:** ![starshipcoder](https://support.routexl.com/letter_avatar_proxy/v4/letter/s/f04885/32.png) [@starshipcoder](https://support.routexl.com/u/starshipcoder)\
**Post date:** [January 23, 2023, 8:52am UTC](https://support.routexl.com/t/route-not-feasible-why/2433/3 "2023-01-23T08:52:54Z")

</div>

This restriction is because the visited point are closed during lunch (12h-14h, and the route start at 9h)  
The restrictions are set by my users

---

<div class="post-metadata">

**Author:** ![RouteXL](https://support.routexl.com/user_avatar/support.routexl.com/routexl/32/347_2.png) [@RouteXL](https://support.routexl.com/u/RouteXL)\
**Post date:** [January 23, 2023, 12:46pm UTC](https://support.routexl.com/t/route-not-feasible-why/2433/4 "2023-01-23T12:46:37Z")

</div>

The infeasible comes from the last location before the return point, that is:

`8: {name: 4, arrival: 170, distance: 67}`

The arrival 170 is before its _inverted_ time restriction of due 180, so that’s good and no waiting time is added. However, with its service time of 15 the departure time becomes 185, which makes it _infeasible_ as the lunch closure has started.

So, it seems to be a specific issue, with inverted time restrictions only. The algorithm does not add waiting time for a due time, only for ready time. This is something we’ll look into, we either need to add waiting time or mark the route feasible.

---

<div class="post-metadata">

**Author:** ![starshipcoder](https://support.routexl.com/letter_avatar_proxy/v4/letter/s/f04885/32.png) [@starshipcoder](https://support.routexl.com/u/starshipcoder)\
**Post date:** [November 15, 2023, 3:39pm UTC](https://support.routexl.com/t/route-not-feasible-why/2433/5 "2023-11-15T15:39:07Z")

</div>

Hi,

Another user fall into the same problem, because no waiting time for due time

Is there a plan to manage it ?

 ![WhatsApp Image 2023-11-15 at 16.09.13](https://support.routexl.com/uploads/default/original/1X/e491c6bfd62e15b48c7dc2da9dc48baf2630a016.jpeg)

---

<div class="post-metadata">

**Author:** ![RouteXL](https://support.routexl.com/user_avatar/support.routexl.com/routexl/32/347_2.png) [@RouteXL](https://support.routexl.com/u/RouteXL)\
**Post date:** [November 15, 2023, 8:33pm UTC](https://support.routexl.com/t/route-not-feasible-why/2433/6 "2023-11-15T20:33:49Z")

</div>

It’s on our list to work on, but we can not give any time line at this moment.

---

<div class="post-metadata">

**Author:** ![starshipcoder](https://support.routexl.com/letter_avatar_proxy/v4/letter/s/f04885/32.png) [@starshipcoder](https://support.routexl.com/u/starshipcoder)\
**Post date:** [March 8, 2024, 4:55pm UTC](https://support.routexl.com/t/route-not-feasible-why/2433/7 "2024-03-08T16:55:07Z")

</div>

Hi, have you any news for this problem

Some users complain about route not working in this case

Have a nice day

---

<div class="post-metadata">

**Author:** ![RouteXL](https://support.routexl.com/user_avatar/support.routexl.com/routexl/32/347_2.png) [@RouteXL](https://support.routexl.com/u/RouteXL)\
**Post date:** [March 8, 2024, 11:25pm UTC](https://support.routexl.com/t/route-not-feasible-why/2433/8 "2024-03-08T23:25:53Z")

</div>

Unfortunately no news, we’re sorry.
