Hi,
I noticed that if a operator is in the middle of a travel to location task and the task is aborted then the kinematics are not stopped if the operator is using "Use navigator for offset travel" option. So the result is that the operator "slides" to the destination although the task sequence is aborted and then FlexSim gives and exception from the OnDestinationArrival event.
See the attached model where this happens. I create a box into Queue1 and the onEntry of Queue1 creates a TRAVELTOLOC task for the operator. Source2 creates a box into Queue3 which onEntry aborts the task sequence of the operator.
I can bypass this by using the normal task executer offset travel logic for the other cases, but if I want to use AStar or network nodes for the offset travel I cannot. At least if I would have AStar in my model I most probably would want to use AStar for offset travel.
Model using AStar and "Use navigator for offset travel"
Thank you for checking this!
Kind regards,
Axel
