# Communication Issues Due to Broken Tags **URL:** \ **Category:** Ignition\ **Tags:** vision\ **Created:** [July 21, 2026, 12:52pm UTC](https://forum.inductiveautomation.com/t/communication-issues-due-to-broken-tags/116477 "2026-07-21T12:52:25Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ttoth](https://avatars.discourse-cdn.com/v4/letter/t/e274bd/32.png) [@ttoth](https://forum.inductiveautomation.com/u/ttoth)\ **Post date:** [July 21, 2026, 12:52pm UTC](https://forum.inductiveautomation.com/t/communication-issues-due-to-broken-tags/116477/1 "2026-07-21T12:52:26Z")
Using vision 8.1.27 I have been having communication issues between ignition and PLC. For a while I could see Good\_Overload quality on some tags in the tag browser and I found 2 tags that were errored in Ignition because they did not exist in the PLC. I understand how that could cause issues since the tags will keep trying to read. I can see in the PLC diagnostic buffer that I get an error "OPC UA Server: Sampling rate could not be reached" and after deleting those two broken tags I saw an improvement in the amount of errors in the PLC. I also found some tags that were ignition expression tags that used a tag from the ignition tag browser (OPC tag) that no longer existed. I saw an improvement deleting those tags as well but I feel like there is another variable I am missing because technically the expression tags don't have an address to poll. Could those broken expression tags cause sample rate issues as well? Also, is there any message in the ignition log files I can search to see if there are more broken tags? I don't see any log messages relating to this, but when I am filtering with INFO I have a lot of data that is unrelated and it is difficult to search through. Is there a term I could search to find it? There are no logs under ERROR or WARN. Thanks in advance! ---
**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:** [July 21, 2026, 1:10pm UTC](https://forum.inductiveautomation.com/t/communication-issues-due-to-broken-tags/116477/2 "2026-07-21T13:10:26Z")
> [@ttoth](#): > > Could those broken expression tags cause sample rate issues as well? No, those errors will be internal to Ignition. > [@ttoth](#): > > I can search to see if there are more broken tags? I think you should upgrade Ignition to a version that includes the Tag Report Tool in the designer tag browser. This lets you search for tags across the system that have bad quality so you can prune them (or correct their problems). ---
**Author:** ![ttoth](https://avatars.discourse-cdn.com/v4/letter/t/e274bd/32.png) [@ttoth](https://forum.inductiveautomation.com/u/ttoth)\ **Post date:** [July 21, 2026, 1:45pm UTC](https://forum.inductiveautomation.com/t/communication-issues-due-to-broken-tags/116477/3 "2026-07-21T13:45:16Z")
Thank you! Yes, I have the tag report tool and I found the two broken OPC references this way but was specifically searching for OPC tags, so I didn't notice the other broken expression tags. It is strange that after deleting the expression tags I saw such a big difference in the amount of sample rate errors in the PLC. There must be something I am missing ---
**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:** [July 21, 2026, 1:56pm UTC](https://forum.inductiveautomation.com/t/communication-issues-due-to-broken-tags/116477/4 "2026-07-21T13:56:48Z")
Are you using leased tags? An expression tag that references an leased OPC tag will move that source to its leased rate. Deleting a bunch of expressions might have impacted your OPC subscriptions. ---
**Author:** ![ttoth](https://avatars.discourse-cdn.com/v4/letter/t/e274bd/32.png) [@ttoth](https://forum.inductiveautomation.com/u/ttoth)\ **Post date:** [July 21, 2026, 2:07pm UTC](https://forum.inductiveautomation.com/t/communication-issues-due-to-broken-tags/116477/5 "2026-07-21T14:07:03Z")
All tag groups are using Direct mode ---
**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:** [July 21, 2026, 2:10pm UTC](https://forum.inductiveautomation.com/t/communication-issues-due-to-broken-tags/116477/6 "2026-07-21T14:10:41Z")
Were there events monitoring the expressions and producing writes to the PLC? (About out of ideas.) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [July 21, 2026, 2:12pm UTC](https://forum.inductiveautomation.com/t/communication-issues-due-to-broken-tags/116477/7 "2026-07-21T14:12:51Z")
What problem are you actually trying to diagnose/solve here? That you receive Good\_Overload quality sometimes? ---
**Author:** ![ttoth](https://avatars.discourse-cdn.com/v4/letter/t/e274bd/32.png) [@ttoth](https://forum.inductiveautomation.com/u/ttoth)\ **Post date:** [July 21, 2026, 2:22pm UTC](https://forum.inductiveautomation.com/t/communication-issues-due-to-broken-tags/116477/8 "2026-07-21T14:22:56Z")
I know the good\_overload status comes from the PLC and I could see there were a lot of errors for sample rate could not be reached. I can understand that the two tags I deleted in Ignition that were setup as OPC tags but no longer existed in the PLC would help with this, but after I did that I still saw a lot of sample rate errors in the PLC. Today, I only have a handful and haven't made any further changes aside from deleting tags that were expressions which I did not think would improve anything. I was trying to figure out if this would actually improve the issue? Or I have fallen down the wrong hole and am investigating something that wouldn't actually affect this.