# Why does the same event date keep alternating between the same values across updates without converging?

**URL:** <https://community.dockflow.com/t/why-does-the-same-event-date-keep-alternating-between-the-same-values-across-updates-without-converging/144>\
**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-the-same-event-date-keep-alternating-between-the-same-values-across-updates-without-converging/144 "2026-11-06T15:07:38Z")\
**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-the-same-event-date-keep-alternating-between-the-same-values-across-updates-without-converging/144/1 "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 value in an update, changes to a different value in the next update, then returns to the earlier value in a later update. Across successive updates, the same event keeps alternating between those values and never converges. This is not the carrier revising its own estimate; the event reading itself is inconsistent from update to update.