frosch wrote:

The orders of the trains say "unload and leave empty".
Adjust the orders if you did not meant to order them to do that.

This comment was imported from FlySpray: https://bugs.openttd.org/task/5901#comment13032

Jam35 wrote:

See train # 129.
(Full load any cargo)

This comment was imported from FlySpray: https://bugs.openttd.org/task/5901#comment13033

Jam35 wrote:

Please check train # 129

This comment was imported from FlySpray: https://bugs.openttd.org/task/5901#comment13034

frosch wrote:

Ah, it is loading at the same station as it unloads.
I think that used to work, but was disabled for cdist or something. Likely should still work, if cdist is disabled.

This comment was imported from FlySpray: https://bugs.openttd.org/task/5901#comment13035

Jam35 wrote:

That trains only purpose is to remove the erroneous cargo.
The cargo could be sent anywhere but I cannot load it :)

This comment was imported from FlySpray: https://bugs.openttd.org/task/5901#comment13036

fonsinchen wrote:

Do you remember how the waiting cargo got there? It has an invalid station, but not the constant INVALID_STATION (which it should have) as its next hop. I wonder how that happened.

This comment was imported from FlySpray: https://bugs.openttd.org/task/5901#comment13037

Jam35 wrote:

Unfortunately I was not online at the time the cargo got there.
A team member says that the cargo acceptance was lost there for a short time, hence cargo is at the station.
We obviously have no idea why it cannot now be picked up as usual.

This comment was imported from FlySpray: https://bugs.openttd.org/task/5901#comment13038

fonsinchen wrote:

Apparently it used the wrong part of the loaded_at_xy / next_station union when inserting into the map. The numbers match up quite nicely then.

This comment was imported from FlySpray: https://bugs.openttd.org/task/5901#comment13039

fonsinchen closed the ticket.

Reason for closing: Fixed

in r26327

This comment was imported from FlySpray: https://bugs.openttd.org/task/5901