# SLC 505 tags bad quality when not viewed **URL:** \ **Category:** Ignition\ **Created:** [August 16, 2019, 7:42pm UTC](https://forum.inductiveautomation.com/t/slc-505-tags-bad-quality-when-not-viewed/27530 "2019-08-16T19:42:19Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kyle.lasher](https://avatars.discourse-cdn.com/v4/letter/k/779978/32.png) [@kyle.lasher](https://forum.inductiveautomation.com/u/kyle.lasher)\ **Post date:** [August 16, 2019, 7:42pm UTC](https://forum.inductiveautomation.com/t/slc-505-tags-bad-quality-when-not-viewed/27530/1 "2019-08-16T19:42:19Z")
We have tags being logged via tag historian whose data integrity is 32 (waiting) when they are not actively present on an active screen. When I open a screen with a control bound to the tag or I navigate to the tag in my tag browser the data integrity changes to 192 and it starts logging data again. What could cause this? The tags are from a SLC 505. The connection to the controller is listed as Connected: Protocol: Direct. Using version 7.9.6 The CPU and Memory trend are both low (1% and \<900mb respectively) ---
**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:** [August 16, 2019, 8:23pm UTC](https://forum.inductiveautomation.com/t/slc-505-tags-bad-quality-when-not-viewed/27530/2 "2019-08-16T20:23:58Z")
That usually means someone set up a leased scan class, and it’s slow rate is too slow for your history needs. ---
**Author:** ![kyle.lasher](https://avatars.discourse-cdn.com/v4/letter/k/779978/32.png) [@kyle.lasher](https://forum.inductiveautomation.com/u/kyle.lasher)\ **Post date:** [August 19, 2019, 11:56am UTC](https://forum.inductiveautomation.com/t/slc-505-tags-bad-quality-when-not-viewed/27530/3 "2019-08-19T11:56:15Z")
That was it. I forgot about that feature. Thanks for the help.