This case needs you, and it is the one most often mistaken for a fault in Dockflow.
When a container is rolled onto a different sailing under a new booking, the old reference still
describes the old journey. Dockflow keeps tracking it, correctly, and the shipment sits on a vessel
that no longer carries your cargo.
What to do: add the new booking or B/L to the tradeflow and remove the old one. Once the
superseded reference is gone, Dockflow retrieves tracking against the remaining one. This is the same
mechanism described in
unexpected or missing containers on a B/L - two references on one
tradeflow pull in two journeys.
If both the old and the new reference stay on the tradeflow, you get the containers, vessel and dates
of both journeys mixed together. That usually shows up as a destination or vessel that belongs to a
file you are not looking at.
Example
A container is rolled onto a different sailing under a new booking. The old reference stays on the tradeflow, so Dockflow keeps tracking the old journey and shows a vessel that no longer carries the cargo. Add the new booking or B/L and remove the old reference; with only the remaining reference, tracking follows the correct journey.