# Historian On Change Tag with Consecutive Duplicates

**URL:** <https://forum.inductiveautomation.com/t/historian-on-change-tag-with-consecutive-duplicates/33673>\
**Category:** Ignition\
**Created:** [April 3, 2020, 7:08pm UTC](https://forum.inductiveautomation.com/t/historian-on-change-tag-with-consecutive-duplicates/33673 "2020-04-03T19:08:50Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![dion.botha](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@dion.botha](https://forum.inductiveautomation.com/u/dion.botha)\
**Post date:** [April 5, 2020, 12:04am UTC](https://forum.inductiveautomation.com/t/historian-on-change-tag-with-consecutive-duplicates/33673/5 "2020-04-05T00:04:00Z")

</div>

I think what is happening is that the tag has its last value stored in history then the device loses connection (On Change triggered), it then logs the same value but with bad quality then the device reconnects, on change is triggered again and it logs the same value with good quality again. I will verify if this is the case on Monday.

I cam across this [http://forum.inductiveautomation.com/t/table-tag-history-and-bad-quality/4319](http://forum.inductiveautomation.com/t/table-tag-history-and-bad-quality/4319)

But even if I could filter out the bad quality, I will still have consecutive duplicates each time the device loses connection and reconnects (just one less).

---

_[View the full topic](https://forum.inductiveautomation.com/t/historian-on-change-tag-with-consecutive-duplicates/33673)._