# Historian tag entry duplicates **URL:** \ **Category:** Ignition\ **Created:** [January 28, 2025, 8:00am UTC](https://forum.inductiveautomation.com/t/historian-tag-entry-duplicates/101473 "2025-01-28T08:00:28Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![djs](https://avatars.discourse-cdn.com/v4/letter/d/e47774/32.png) [@djs](https://forum.inductiveautomation.com/u/djs)\ **Post date:** [January 28, 2025, 7:07pm UTC](https://forum.inductiveautomation.com/t/historian-tag-entry-duplicates/101473/6 "2025-01-28T19:07:03Z")
I don't recommend this approach for anything in production that you plan to support or maintain, because as already stated it is unsupported and could break at any time. However... If you really need the historian to update its cache, you can just restart the historian. As in, edit the config on the gateway and save it again. If you watch the logs, you'll see these entries: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/2/42e5178ecb4453d8d93fd4bc0a212460a477f561.png) which should make it use what you updated in the table. Or if you want an even less stable solution, you could automate it with this: > [@system.tag.storeTagHistory() Creating duplicate IDs in sqlth\_te](https://forum.inductiveautomation.com/t/system-tag-storetaghistory-creating-duplicate-ids-in-sqlth-te/93857/2): > > For anyone curious. This function called from the gateway scope will "restart" the history provider: from com.inductiveautomation.ignition.gateway import IgnitionGateway def restartHist(prov): context = IgnitionGateway.get() tagHistMan = context.getTagHistoryManager() tagHistProv = tagHistMan.getTagHistoryProvider(prov) tagHistProv.shutdown() tagHistProv.startup() (Be aware that messing with the historian DB tables or SDK can seriously mess up your historian or gateway.) Use at your own … But again, not something I'd put in production... --- _[View the full topic](https://forum.inductiveautomation.com/t/historian-tag-entry-duplicates/101473)._