# \#data-is-wrong

**URL:** https://community.dockflow.com/tag/data-is-wrong/3.md

[Latest](https://community.dockflow.com/latest.md) · [Categories](https://community.dockflow.com/categories.md) · [Tags](https://community.dockflow.com/tags.md)

---

## [How should I report a merged shipment or a transhipment after the final port when the Console already classes it as an anomaly?](https://community.dockflow.com/t/how-should-i-report-a-merged-shipment-or-a-transhipment-after-the-final-port-when-the-console-already-classes-it-as-an-anomaly/147)

<div class="topic-metadata">

**Author:** [@dockflow](https://community.dockflow.com/u/dockflow)\
**Replies:** 0\
**Last updated:** [November 6, 2026, 3:08pm UTC](https://community.dockflow.com/t/how-should-i-report-a-merged-shipment-or-a-transhipment-after-the-final-port-when-the-console-already-classes-it-as-an-anomaly/147 "2026-11-06T15:08:31Z")

</div>

These are worth reporting: merged shipments, milestones in an impossible order, a plan that starts and ends at the same port, or a transhipment appearing after the final port. These have names and a definition - see an…

---

## [Why is a milestone shown on the carrier’s page missing in Dockflow?](https://community.dockflow.com/t/why-is-a-milestone-shown-on-the-carrier-s-page-missing-in-dockflow/146)

<div class="topic-metadata">

**Author:** [@dockflow](https://community.dockflow.com/u/dockflow)\
**Replies:** 0\
**Last updated:** [November 6, 2026, 3:08pm UTC](https://community.dockflow.com/t/why-is-a-milestone-shown-on-the-carrier-s-page-missing-in-dockflow/146 "2026-11-06T15:08:13Z")

</div>

The carrier’s own page shows an event, the rest of the shipment tracks normally, and that one event is absent. Example A carrier’s page shows a milestone for a shipment. In Dockflow, the rest of the shipment’s events …

---

## [Why is my container shown in the wrong place when the carrier's location code and name disagree?](https://community.dockflow.com/t/why-is-my-container-shown-in-the-wrong-place-when-the-carriers-location-code-and-name-disagree/145)

<div class="topic-metadata">

**Author:** [@dockflow](https://community.dockflow.com/u/dockflow)\
**Replies:** 0\
**Last updated:** [November 6, 2026, 3:07pm UTC](https://community.dockflow.com/t/why-is-my-container-shown-in-the-wrong-place-when-the-carriers-location-code-and-name-disagree/145 "2026-11-06T15:07:56Z")

</div>

Carriers send location codes and names that do not always agree, and some codes are valid identifiers for a completely different place. A leg routed through somewhere implausible for the trade lane is worth reporting; …

---

## [Why does the same event date keep alternating between the same values across updates without converging?](https://community.dockflow.com/t/why-does-the-same-event-date-keep-alternating-between-the-same-values-across-updates-without-converging/144)

<div class="topic-metadata">

**Author:** [@dockflow](https://community.dockflow.com/u/dockflow)\
**Replies:** 0\
**Last updated:** [November 6, 2026, 3:07pm UTC](https://community.dockflow.com/t/why-does-the-same-event-date-keep-alternating-between-the-same-values-across-updates-without-converging/144 "2026-11-06T15:07:38Z")

</div>

Not a carrier revising its own estimate, which is normal, but the same event reading 24/03, then 30/03, then 24/03 again across successive updates, without converging. Example A container’s event date appears as a val…

---

## [Why did a confirmed time change by days after the event?](https://community.dockflow.com/t/why-did-a-confirmed-time-change-by-days-after-the-event/143)

<div class="topic-metadata">

**Author:** [@dockflow](https://community.dockflow.com/u/dockflow)\
**Replies:** 0\
**Last updated:** [November 6, 2026, 3:07pm UTC](https://community.dockflow.com/t/why-did-a-confirmed-time-change-by-days-after-the-event/143 "2026-11-06T15:07:21Z")

</div>

A confirmed actual can still be revised. Revisions of a few hours after confirmation are common and are not a fault. Report it when the change is large - days rather than hours - or when a confirmed arrival ends up da…

---

## [Why does a Dockflow value stay behind the carrier page after repeated refreshes?](https://community.dockflow.com/t/why-does-a-dockflow-value-stay-behind-the-carrier-page-after-repeated-refreshes/142)

<div class="topic-metadata">

**Author:** [@dockflow](https://community.dockflow.com/u/dockflow)\
**Replies:** 0\
**Last updated:** [November 6, 2026, 3:07pm UTC](https://community.dockflow.com/t/why-does-a-dockflow-value-stay-behind-the-carrier-page-after-repeated-refreshes/142 "2026-11-06T15:07:04Z")

</div>

A value trailing the carrier’s own page for a while is normal rather than a defect - that case is explained here. What is worth reporting is a value that stays behind across several days, because that is the shipment n…
