I found a workaround in the mean time. The trick is to remove the current station from the target-pool. You can do this by utilizing the targets of the interrupt to include a "trigger" station that is immediately after the target station. This moves the train just a little bit out of the station ...

I'm seeing the same bug. The idea, based on my understanding of fff-395, is to create an event-driven schedule where one train will visit drop-off points, as stations in a group, until empty and refill at a station when empty.

To emulate the memory of which stations were visited, each station will ...