# Quarantines items - Violation of PRIMARY KEY constraint

**URL:** <https://forum.inductiveautomation.com/t/quarantines-items-violation-of-primary-key-constraint/66852>\
**Category:** Ignition\
**Created:** [November 23, 2022, 2:17pm UTC](https://forum.inductiveautomation.com/t/quarantines-items-violation-of-primary-key-constraint/66852 "2022-11-23T14:17:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vrautomation](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/vrautomation/32/11155_2.png) [@vrautomation](https://forum.inductiveautomation.com/u/vrautomation)\
**Post date:** [November 23, 2022, 2:17pm UTC](https://forum.inductiveautomation.com/t/quarantines-items-violation-of-primary-key-constraint/66852/1 "2022-11-23T14:17:56Z")

</div>

I always had this issue with the historian. Somehow, it try to record the same tag twice.

Ignition 8.1.17 with a redundant node.

I'm about to disable the store&foward because of that.

Someone else have the same issue?

---

<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:** [November 23, 2022, 4:02pm UTC](https://forum.inductiveautomation.com/t/quarantines-items-violation-of-primary-key-constraint/66852/2 "2022-11-23T16:02:39Z")

</div>

Similar to this topic, except for redundancy:

> [@PostGRES SQL Quarantined Items](https://forum.inductiveautomation.com/t/postgres-sql-quarantined-items/45780):
>
> Running version 8.1.3 with PostGres 13.2.1 and I am seeing (repeatedly) what I think is one tag causing issues with historical data being quarantined: ERROR: duplicate key value violates unique constraint "sqlth\_1\_data\_pkey" Detail: Key (tagid, t\_stamp)=(1474, 1618781907679) already exists. This is a new set up and we are not dependent on the data yet, so I have exported examples of this data, then deleted it, and it comes back in a few hours. It is always the same tagid “1474”. I have not pa…

I think "warm" redundancy for tag history is wonky. Might even call it buggy. The trigger option mentioned in that topic might work for you.