# Ignore Bad Quality/Allow Uncertain Quality Data for Historian? **URL:** \ **Category:** Ignition\ **Created:** [January 16, 2026, 5:08pm UTC](https://forum.inductiveautomation.com/t/ignore-bad-quality-allow-uncertain-quality-data-for-historian/113354 "2026-01-16T17:08:44Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![abishur](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/abishur/32/9096_2.png) [@abishur](https://forum.inductiveautomation.com/u/abishur)\ **Post date:** [January 16, 2026, 5:08pm UTC](https://forum.inductiveautomation.com/t/ignore-bad-quality-allow-uncertain-quality-data-for-historian/113354/1 "2026-01-16T17:08:44Z")
I’m using Ignition 8.3.2 with a Siemens S7-1500 PLC and communicating with it via OPC-UA. It’s apparently being overloaded and keeps changing its tags’ quality from ‘Good’ to ‘Good\_Overload(“Sampling has slowed down due to resource limitations”)’. Each time it does this it inserts a new row to the historian database because we have the tags configured for “on change” and ignition regards this a “change” even though the tag value itself hasn’t changed. The result is my partition sizes have swelled from 700MB at most to 60+ GB for 7 days of data. In the past I remember there being a way to tell ignition to not allow Bad Quality Data or not allow uncertain quality data on the History Provider settings. How come this was removed/how can I get access to it again? Going through several thousand tags and using an expression script to force a quality is not a viable solution. ---
**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:** [January 16, 2026, 5:17pm UTC](https://forum.inductiveautomation.com/t/ignore-bad-quality-allow-uncertain-quality-data-for-historian/113354/2 "2026-01-16T17:17:49Z")
This code is neither bad nor uncertain. There's nothing to gain access to. More information: > [@GOOD\_OVERLOAD, should I ignore it?](https://forum.inductiveautomation.com/t/good-overload-should-i-ignore-it/109128/3): > > Your source OPC server is telling you that it isn't keeping up with the workload you've given it. It definitely should not be ignored. > [@Ignition 8.1.5 OPC UA Client Good\_Overload Quality](https://forum.inductiveautomation.com/t/ignition-8-1-5-opc-ua-client-good-overload-quality/46792/2): > > Starting in 8.1.2 Ignition’s QualityCode system gained a Good\_Overload code that is now mapped to when a Good\_Overload StatusCode is received from an OPC UA server. You were likely always receiving this StatusCode on value changes from this server but previously it was just ignored. Slow down your sampling rate (Tag Group rate in Ignition) or just ignore it. The QualityCode is purely informative, it doesn’t have any representation in the tag browser or the quality overlay system. TL/DR: **Fix your overload condition.** Alternative: make expression tags referencing these tags, using `forceQuality()`. ---
**Author:** ![abishur](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/abishur/32/9096_2.png) [@abishur](https://forum.inductiveautomation.com/u/abishur)\ **Post date:** [January 16, 2026, 5:34pm UTC](https://forum.inductiveautomation.com/t/ignore-bad-quality-allow-uncertain-quality-data-for-historian/113354/3 "2026-01-16T17:34:17Z")
Good to know the distinction, I’m working with the client to get the root issue fixed, however it would still be nice to able to not have the historian filling up with 60 GBs of junk data. Logically, if I’m telling it to log “On change” that is a reference to the value of the tag, not the quality of the tag. ---
**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:** [January 16, 2026, 6:17pm UTC](https://forum.inductiveautomation.com/t/ignore-bad-quality-allow-uncertain-quality-data-for-historian/113354/4 "2026-01-16T18:17:56Z")
> [@abishur](#): > > value of the tag, not the quality of the tag. You say "logically", but I find it logical that quality is part of the value. 🤷‍♂️ ---
**Author:** ![abishur](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/abishur/32/9096_2.png) [@abishur](https://forum.inductiveautomation.com/u/abishur)\ **Post date:** [January 16, 2026, 7:13pm UTC](https://forum.inductiveautomation.com/t/ignore-bad-quality-allow-uncertain-quality-data-for-historian/113354/5 "2026-01-16T19:13:37Z")
I could see a point for the overall sentiment, however if you look in the historian, good\_overload and good are both stored with a data integrity of 192. It’s just row after row after row of duplicated data and I would love a way to have the option to disable such data, and even all quality change data based on the needs of the client rather a one size fits all approach. Which brings me back to my original question: > In the past I remember there being a way to tell ignition to not allow Bad Quality Data or not allow uncertain quality data on the History Provider settings. How come this was removed/how can I get access to it again? Going through several thousand tags and using an expression script to force a quality is not a viable solution. ---
**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:** [January 16, 2026, 7:35pm UTC](https://forum.inductiveautomation.com/t/ignore-bad-quality-allow-uncertain-quality-data-for-historian/113354/6 "2026-01-16T19:35:06Z")
> [@abishur](#): > > back to my original question I don't recall that setting, but it is moot, as I already pointed out: Good\_Overload is neither uncertain nor bad.