why not marked UNROUTABLE

[lmmir]

config defaultdispatcher.dismissUnroutableTransportOrders is true ,why not marked UNROUTABLE

[swltr]

See https://www.opentcs.org/docs/6/developer/developers-guide/opentcs-developers-guide.html#_a_transport_orders_life_cycle:

The kernel’s router checks whether routing between the transport order’s destinations is possible at all. If yes, its state is changed to DISPATCHABLE. If routing is not possible, the transport order is marked as UNROUTABLE and not processed any further.

A transport order only becomes UNROUTABLE if it's generally not possible to route between its destinations, e.g. there is no way for any vehicle to get from destination A to destination B. As a result, transport orders with only a single destination can never become UNROUTABLE.

[lmmir]

As a result, transport orders with only a single destination can never become UNROUTABLE. why?

[swltr]

UNROUTABLE is not intended to mark transport orders that are not currently routable for a specific vehicle, as this is something that may change, e.g. by unlocking paths in the plant model. UNROUTABLE is supposed to mark transport orders that are generally not routable, regardless of paths locks and processing vehicles. This is intended behaviour.