You can set the paths to "non-passing" which will enforce a minimum distance between travelers on them. As a shortcut redraw the connection between two network nodes to toggle between passing and non-passing.
You then also have to set the Task Executers to "Do no travel offsets and block space on networks". Otherwise trucks can accumulate at the network nodes.
I am very glad that you helped guide me and make a sample model for me. I'm not good at it. Thank you very much.
I can almost do the same as yours. But I don't know what happened. Why aren't resources restored? Please advise.
The connection ranks coming out of the Split activity matter in this case. The "original" token will continue through the first connector. A resource must be released by the token that acquired it (to be precise, you have to refer to the exact label node to which the resource was assigned). So the "original" token must be the one to enter the Delay and Release activity and the "copy" should be the one that starts the travel task.
This can also make a difference when the tokens are joined again. The token that enters the Join activity through the first connector will always be the one that continues on while all others are deleted. This is important to keep in mind when split tokens update or add new labels.
You can change the rank of connection by clicking on it and adjusting the rank in the properties.
You are the person who can answer the questions most clearly. And I can continue. Thank you very much. Please help answer my questions again. ^^