# 8.1.1 Tag Overlay OPC\_Not\_Connected **URL:** \ **Category:** Ignition\ **Created:** [December 14, 2020, 7:27pm UTC](https://forum.inductiveautomation.com/t/8-1-1-tag-overlay-opc-not-connected/41509 "2020-12-14T19:27:14Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jackson.null](https://avatars.discourse-cdn.com/v4/letter/j/71e660/32.png) [@jackson.null](https://forum.inductiveautomation.com/u/jackson.null)\ **Post date:** [December 14, 2020, 7:27pm UTC](https://forum.inductiveautomation.com/t/8-1-1-tag-overlay-opc-not-connected/41509/1 "2020-12-14T19:27:14Z")
Upgraded from 8.0.11 to 8.1.1. Components bound to opc tags are showing a red tag overlay (OPC\_Not\_Connected) for a several seconds or sometimes indefinitely after switching screens. Using ignition’s opc ua server and ab logix drivers. Tags are set up as leased tags with a 5 second slow rate and 1 second leased rate. Changing a tag to the default direct tag group fixes the issue, but changing the leased tag group to match the default direct tag group has no change. When pressing a button while the tag overlay persists, the value that it’s driving still appears to change and the tag overlay will go away. When this happens when there are other components with tag overlays still present, those overlays will then persist until refreshing the screen. There’s about 20k tags across 37 devices (all ab logix), and 36 clients. All tags are acting the same across every client and device. Changed all the tags in one client project to the default tag group and there’s no longer a problem with the tag overlays in that project. Have tried changing various settings in the gateway and tag groups, with no positive difference. Nothing seems out of the ordinary in the logs or performance of the server as far as I can tell. Have a support ticket in with Inductive Automation, but any other insight would be welcome. Thanks ---
**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:** [December 14, 2020, 8:13pm UTC](https://forum.inductiveautomation.com/t/8-1-1-tag-overlay-opc-not-connected/41509/2 "2020-12-14T20:13:56Z")
Try changing your stale timeout to longer than the slow rate. ---
**Author:** ![jackson.null](https://avatars.discourse-cdn.com/v4/letter/j/71e660/32.png) [@jackson.null](https://forum.inductiveautomation.com/u/jackson.null)\ **Post date:** [December 14, 2020, 8:29pm UTC](https://forum.inductiveautomation.com/t/8-1-1-tag-overlay-opc-not-connected/41509/3 "2020-12-14T20:29:43Z")
Was this setting moved when they changed the scan class editor to the tag group editor? I’m not seeing a stale timeout or threshold in the new tag group editor. ---
**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:** [December 14, 2020, 8:50pm UTC](https://forum.inductiveautomation.com/t/8-1-1-tag-overlay-opc-not-connected/41509/4 "2020-12-14T20:50:58Z")
Well, shoot. I didn’t notice the disappearance of this property. ---
**Author:** ![Paullys50](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paullys50/32/3324_2.png) [@Paullys50](https://forum.inductiveautomation.com/u/Paullys50)\ **Post date:** [December 17, 2020, 4:31pm UTC](https://forum.inductiveautomation.com/t/8-1-1-tag-overlay-opc-not-connected/41509/5 "2020-12-17T16:31:42Z")
I'm seeing the same thing with stale overlays on screen load in my development test environment. This had been fixed in 8.0.4/7 but seems to be broken again. > [@\[BUG-13815, 15230\]Components showing stale tag overlay when they first appear in a window](http://forum.inductiveautomation.com/t/bug-13815-15230-components-showing-stale-tag-overlay-when-they-first-appear-in-a-window/26298/16): > > The 8.0.7 nightly build from today contains a change that is relevant to the overlay issue presented here earlier. In short, null values on initial load were categorized as bad quality instead of uncertain quality, which is why the red overlays were appearing. There will still be overlays while bindings are loading, but they should use the grey overlay. @zxcslo this change doesn’t really impact your case, since the error your seeing in the GIF is showing an unsupported operand exception due to… ---
**Author:** ![jackson.null](https://avatars.discourse-cdn.com/v4/letter/j/71e660/32.png) [@jackson.null](https://forum.inductiveautomation.com/u/jackson.null)\ **Post date:** [March 2, 2021, 4:27pm UTC](https://forum.inductiveautomation.com/t/8-1-1-tag-overlay-opc-not-connected/41509/6 "2021-03-02T16:27:57Z")
I’m pretty sure this issue was caused by our server. Our primary server failed recently and we loaded ignition on a dummy pc temporarily which had no issues with overlays. Once our new primary server was set up for production, we transferred our license to it and had the same problem with leased tags. The vm on the new server was set up identical to the old server when we had this issue originally. Our cpu was running 90-101% (old server was around 60%) and causing more general latency related issues with our clients than before when we had just the overlay problem. Memory usage looked ok on the ignition browser trend, but on task manager it looked near maxed, although some of the numbers were deceptive on there. the vm was given another cpu core to work with and the dynamic ram was changed to static 16gb. Cpu usage went down considerably, hovering in the 30% range, and the memory trend looks like it’s operating more efficiently. In any event, we have changed all of our tags back to leased and are not experiencing any more overlay issues.