# \[IGN-15688\] Did the tag timestamp change in its core functionality?

**URL:** <https://forum.inductiveautomation.com/t/ign-15688-did-the-tag-timestamp-change-in-its-core-functionality/114447>\
**Category:** Ignition\
**Tags:** ignition83\
**Created:** [March 11, 2026, 4:20pm UTC](https://forum.inductiveautomation.com/t/ign-15688-did-the-tag-timestamp-change-in-its-core-functionality/114447 "2026-03-11T16:20:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eric\_Leisebein](https://avatars.discourse-cdn.com/v4/letter/e/e5b9ba/32.png) [@Eric\_Leisebein](https://forum.inductiveautomation.com/u/Eric_Leisebein)\
**Post date:** [March 11, 2026, 4:20pm UTC](https://forum.inductiveautomation.com/t/ign-15688-did-the-tag-timestamp-change-in-its-core-functionality/114447/1 "2026-03-11T16:20:19Z")

</div>

I updated our production environment from 8.1.48 to 8.3.4.  
Almost everything went smoothly when doing so (I had to refresh the license, which was no big deal).  
I just noticed that after the update some timestamps of dataset type tags don’t update anymore, when the underlying dataset data doesn’t change. Meaning that before the update you could write to one of these tags and even if you wrote the same data that was on the tag before, the timestamp would change. Now it only does, if the data actually differs from before.  
The same is with DB dataset tags. In the past the timestamps would update with every poll, regardless of the underlying data. Now it only does with actual changes in the data.

Now I don’t know if this is intentional and an actual bugfix or if this introduced a new bug.  
I am a bit puzzled.

---

<div class="post-metadata">

**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\
**Post date:** [March 11, 2026, 6:29pm UTC](https://forum.inductiveautomation.com/t/ign-15688-did-the-tag-timestamp-change-in-its-core-functionality/114447/2 "2026-03-11T18:29:04Z")

</div>

If the deadband is enabled on the tag, then the timestamp will not update if nothing has changed (even on a Dataset) in 8.3. If it is turned off, then the timestamp will be replaced. It is a difference in behavior from 8.1 and I will open a ticket to have it discussed.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [March 11, 2026, 6:35pm UTC](https://forum.inductiveautomation.com/t/ign-15688-did-the-tag-timestamp-change-in-its-core-functionality/114447/3 "2026-03-11T18:35:29Z")

</div>

I vaguely recall this being a feature request. I'm sure it also reduces churn in the persistence system.

---

<div class="post-metadata">

**Author:** ![Eric\_Leisebein](https://avatars.discourse-cdn.com/v4/letter/e/e5b9ba/32.png) [@Eric\_Leisebein](https://forum.inductiveautomation.com/u/Eric_Leisebein)\
**Post date:** [March 12, 2026, 9:13am UTC](https://forum.inductiveautomation.com/t/ign-15688-did-the-tag-timestamp-change-in-its-core-functionality/114447/4 "2026-03-12T09:13:35Z")

</div>

Thanks for the hint.  
I deactivated the deadband and now it works like it did before.