# Records keep being placed in the Store and Forward quarantine

**URL:** <https://forum.inductiveautomation.com/t/records-keep-being-placed-in-the-store-and-forward-quarantine/115901>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [June 9, 2026, 9:18am UTC](https://forum.inductiveautomation.com/t/records-keep-being-placed-in-the-store-and-forward-quarantine/115901 "2026-06-09T09:18:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![manuele.longhi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/manuele.longhi/32/51470_2.png) [@manuele.longhi](https://forum.inductiveautomation.com/u/manuele.longhi)\
**Post date:** [June 9, 2026, 9:18am UTC](https://forum.inductiveautomation.com/t/records-keep-being-placed-in-the-store-and-forward-quarantine/115901/1 "2026-06-09T09:18:19Z")

</div>

Hello all,  
I am running into some issues regarding the store and forward quarantine.

**Setup**  
I have a machine UDT with

1. Several tags that change very slowly (once per day/week or slower)
2. A production bit (true/false)

History is enabled for all of these tags (and they are connected to a database that is consistently available)

**Problem**  
Every time my production bit transitions from 0 to 1, 25 (the **Write Size** ) new elements are placed in the quarantine file. Analyzing the quarantine file I have noticed that every new batch of data

- Always involve the same tags
- Every tag has the exact same value in each batch
- Every tag has the exact same timestamp in each batch

 ![Quarantena](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/d/fd13e028619b5b7155e20acaa0ded9ec06551391.png)  
_Sensitive data has been redacted_

This seems to only happen on the rising edge of the production bit. The slow-changing tags do not actually change value in that moment, so I would not expect any new history record to be generated.

Moreover, the reason why these items are placed in the quarantine is "duplicate key" error, which makes sense since data in the quarantine file actually **is** in the database.

Why then does Ignition keep trying to save these items when the production bit goes to 1? And why doesn't the same behavior happen when it goes to 0?

If you need any additional detail on how the system is configured, please let me know

---

<div class="post-metadata">

**Author:** ![djs](https://avatars.discourse-cdn.com/v4/letter/d/e47774/32.png) [@djs](https://forum.inductiveautomation.com/u/djs)\
**Post date:** [June 9, 2026, 6:57pm UTC](https://forum.inductiveautomation.com/t/records-keep-being-placed-in-the-store-and-forward-quarantine/115901/2 "2026-06-09T18:57:58Z")

</div>

Can you provide the json of your UDT definition?

---

<div class="post-metadata">

**Author:** ![manuele.longhi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/manuele.longhi/32/51470_2.png) [@manuele.longhi](https://forum.inductiveautomation.com/u/manuele.longhi)\
**Post date:** [June 10, 2026, 7:20am UTC](https://forum.inductiveautomation.com/t/records-keep-being-placed-in-the-store-and-forward-quarantine/115901/3 "2026-06-10T07:20:41Z")

</div>

Unfortunately I cannot load the exact copy of the UDT, as it has some sensitive data. I had to doctor it a little (as in removed some tags and renamed the parameters). The core and configurations are the same.

[MachineUDT.json](https://forum.inductiveautomation.com/uploads/short-url/dGYWeY1OUsGx0zoA40yBIPIzoc4.json) (5.4 KB)

Let me know if there's anything else that you need