Yeah, I realize that now, misinterpreting cause and effect, thanks for the pointers, I've got things ticking over better now. (Moved over to a rooted system where trains have a 'home' station that is always enabled, and they only depart the station when resources start getting low, and acknowledge ...

Hmm, true that is more a product of the 'orphaned' system than of it skipping destinations, and if there is no valid destination for the train BESIDES the home station it's a symptom of having too many trains/too few output stations for them to collect from, I'm seeing a problem and misunderstanding ...

So, in my network I am using trains that have a destination list that simply looks like this:

Output: Iron Ore [Until full, OR 15 seconds has passed]
Input: Iron Ore [Until empty, OR 15 seconds has passed]

All of the destinations that accept or create a resource on the network, share the same ...