Loco was set to go through station with 2 cargo wagons attached, loco made it through but wagons didn't, station showed WARNING.

Removed receive station and incurred error:

The mod Rift Rail (0.7.27) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event RiftRail::on_tick (ID 0)
Trying to change direction of automatic train moving on a path.
stack traceback:
[C]: in function 'newindex'
__RiftRail/scripts/teleport.lua:473: in function 'restore_train_state'
RiftRail/scripts/teleport.lua:547: in function 'finalize_sequence'
RiftRail/scripts/teleport.lua:609: in function 'process_transfer_step'
RiftRail/scripts/teleport.lua:1044: in function 'process_teleport_sequence'
RiftRail/scripts/teleport.lua:1074: in function 'on_tick'
RiftRail/control.lua:179: in function <RiftRail/control.lua:177>

Thank you. I'll check it out.

I can imagine why the error occurred, but I can't reproduce it. I built a similar scenario based on your description, but it didn't crash, which I find very strange. I created a train consisting of one locomotive and four carriages, first transferring the locomotive, then removing the station, and everything worked fine. Did I do something wrong?

I've found the problem. It's because the railway is bidirectional, right? After removing the current station, the train has to reverse to reach the next station. This is indeed a problem, and I haven't figured out how to solve it yet. Currently, setting up one-way traffic lights prevents the error from triggering. I'll look into it further. But a solution might be a little later.

Sorry for the long wait, but I think this issue should finally be fixed now. I rarely encounter this problem myself, and most importantly, hard to find a safe way to apply speed and direction to exiting trains, taking into account schdule changes and many other factors. So, it's temporarily more stable now.