# SQLTag History Data: Quarantined items

**URL:** <https://forum.inductiveautomation.com/t/sqltag-history-data-quarantined-items/43750>\
**Category:** Ignition\
**Tags:** database, ignition80\
**Created:** [February 23, 2021, 8:30pm UTC](https://forum.inductiveautomation.com/t/sqltag-history-data-quarantined-items/43750 "2021-02-23T20:30:46Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jsalceda](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@jsalceda](https://forum.inductiveautomation.com/u/jsalceda)\
**Post date:** [February 23, 2021, 8:30pm UTC](https://forum.inductiveautomation.com/t/sqltag-history-data-quarantined-items/43750/1 "2021-02-23T20:30:46Z")

</div>

Hello, today we upgrated our system to Ignition 8.1.2 from Ignition 8.1.0. As soon as the gateway restarted, we saw quarantined items starting to pop up in the Store and Forward section with the following error description:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/6/f6ce3f7a9cee3b9c73fce3d0cab08aef4db23067.png)

We browsed through the forums and saw that this issue is usually caused by multiple instances of an Ignition system executing with an identical configuration. However, this is not our case, we don’t have a backup Ignition instance running. We tried restarting the whole gateway and system but the error still occurs.

We tried deleting the quarantined items (after exporting), but new quarantined data keeps being added by the minute.

The error involves multiple tags, not a specific tag, which we saw happening in a couple of other forum posts, any recommendations to solve this problem is highly appreciated.

---

<div class="post-metadata">

**Author:** ![ant1](https://avatars.discourse-cdn.com/v4/letter/a/5e9695/32.png) [@ant1](https://forum.inductiveautomation.com/u/ant1)\
**Post date:** [February 25, 2021, 5:03pm UTC](https://forum.inductiveautomation.com/t/sqltag-history-data-quarantined-items/43750/2 "2021-02-25T17:03:55Z")

</div>

We too are experiencing this, interestingly all our tags are sourced through MQTT, we went from 8.1.1 to 8.1.2. I have raised a support ticket

---

<div class="post-metadata">

**Author:** ![jsalceda](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@jsalceda](https://forum.inductiveautomation.com/u/jsalceda)\
**Post date:** [February 25, 2021, 5:54pm UTC](https://forum.inductiveautomation.com/t/sqltag-history-data-quarantined-items/43750/3 "2021-02-25T17:54:18Z")

</div>

I raised a support ticket as well, I’ll update you once I receive a response.

---

<div class="post-metadata">

**Author:** ![jsalceda](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@jsalceda](https://forum.inductiveautomation.com/u/jsalceda)\
**Post date:** [February 26, 2021, 9:38pm UTC](https://forum.inductiveautomation.com/t/sqltag-history-data-quarantined-items/43750/4 "2021-02-26T21:38:48Z")

</div>

Hello @ant1, have you solved your problem?

---

<div class="post-metadata">

**Author:** ![ant1](https://avatars.discourse-cdn.com/v4/letter/a/5e9695/32.png) [@ant1](https://forum.inductiveautomation.com/u/ant1)\
**Post date:** [February 27, 2021, 8:17pm UTC](https://forum.inductiveautomation.com/t/sqltag-history-data-quarantined-items/43750/5 "2021-02-27T20:17:03Z")

</div>

Hello @jsalceda, no not yet, still awaiting a response from Support. As I touched on, the only tags causing us errors are all sourced from the MQTT Engine Module, out of curiosity, is this the same with your tags?

---

<div class="post-metadata">

**Author:** ![jsalceda](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@jsalceda](https://forum.inductiveautomation.com/u/jsalceda)\
**Post date:** [March 1, 2021, 5:24pm UTC](https://forum.inductiveautomation.com/t/sqltag-history-data-quarantined-items/43750/6 "2021-03-01T17:24:40Z")

</div>

No, in our case the tags were not sourced through MQTT, after the quarantined data issue, we started to have extreme clock drifts in our system, which degraded performance greatly. We tried to restore our gateway multiple times (in the same version, 8.1.2), but the only thing that helped up get rid of the problem was restoring to our previous version of Ignition, 8.1.0.
