# Why does a Dockflow value stay behind the carrier page after repeated refreshes?

**URL:** <https://community.dockflow.com/t/why-does-a-dockflow-value-stay-behind-the-carrier-page-after-repeated-refreshes/142>\
**Category:** How-to Q&A\
**Tags:** data-is-wrong, area-tracking-data\
**Created:** [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")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dockflow](https://community.dockflow.com/letter_avatar_proxy/v4/letter/d/a9a28c/32.png) [@dockflow](https://community.dockflow.com/u/dockflow)\
**Post date:** [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/1 "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](https://community.dockflow.com/tag/data-differs-from-carrier). What is worth reporting is a value that stays  
behind across several days, because that is the shipment no longer being updated at all.

**Example**  
A shipment’s status shows an earlier stage than the carrier’s own page. Several days later it is still behind. Report it with the reference, because the shipment may no longer be updating.