# Tag History: Multiple values getting stored with same timestamp

**URL:** <https://forum.inductiveautomation.com/t/tag-history-multiple-values-getting-stored-with-same-timestamp/102548>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [February 19, 2025, 11:01am UTC](https://forum.inductiveautomation.com/t/tag-history-multiple-values-getting-stored-with-same-timestamp/102548 "2025-02-19T11:01:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lars\_Witte](https://avatars.discourse-cdn.com/v4/letter/l/8dc957/32.png) [@Lars\_Witte](https://forum.inductiveautomation.com/u/Lars_Witte)\
**Post date:** [February 19, 2025, 11:01am UTC](https://forum.inductiveautomation.com/t/tag-history-multiple-values-getting-stored-with-same-timestamp/102548/1 "2025-02-19T11:01:59Z")

</div>

I'm getting very frequent erros on my gateway:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/1/81b6bad66bf469d87cd6fa05cce93e65fa9db1d3.png)

with the message:  
"The timestamp 'timestamp' has already been stored for tag 'tagname' "  
It happens with multiple tags and over the last few days the error has happened 248 times.

The tags that get flagged in the error messages have all been setup with a periodic sample mode and usually a sample rate of 2 seconds.  
I would understand if it logged the values on change with no minimum time between samples, but that's not the case.

Under the store and forward menu I can retry sending the quarantined values and it will send it to the database without any issues.

The data is being sent to an SQLite database which we have no other issues with.  
I cant seem to find any posts about this on the forum, but maybe someone else has had the issue in the past and then found a solution for themselves.

---

<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:** [February 19, 2025, 1:14pm UTC](https://forum.inductiveautomation.com/t/tag-history-multiple-values-getting-stored-with-same-timestamp/102548/2 "2025-02-19T13:14:43Z")

</div>

Extremely common problem if device connections are unstable, or if a device's OPC server is delivering data with quality code "Good, Overload".

Under no circumstances should you ever log history to a SQLite database. That technology is **single-threaded** and will utterly choke if you push it even a little. SQLite is designed to be used as storage for application **configuration** , not for dynamic data.

---

<div class="post-metadata">

**Author:** ![Lars\_Witte](https://avatars.discourse-cdn.com/v4/letter/l/8dc957/32.png) [@Lars\_Witte](https://forum.inductiveautomation.com/u/Lars_Witte)\
**Post date:** [February 24, 2025, 7:31am UTC](https://forum.inductiveautomation.com/t/tag-history-multiple-values-getting-stored-with-same-timestamp/102548/3 "2025-02-24T07:31:03Z")

</div>

Thank you, that makes perfect sense.