question

@david.chan,

When a task executer on a network node path is stopped, he disconnects from the network. When he is resumed, he reconnects to the network and travels directly to his next node. He is no longer on the network node path. This is a limitation of how the default network navigator works.

If you want different behavior, then you would need to use a different navigator, such as the AGV Navigator.

You could also not stop a traveler in the middle of an edge. Instead of stopping the operator immediately, add logic to stop the operator at a future point, such as saving a label on the operator and stopping him in a different trigger if that label is set.