# Report: Unused tags?

**URL:** <https://forum.inductiveautomation.com/t/report-unused-tags/83711>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [January 2, 2024, 8:08pm UTC](https://forum.inductiveautomation.com/t/report-unused-tags/83711 "2024-01-02T20:08:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![brians.laptop](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/brians.laptop/32/27906_2.png) [@brians.laptop](https://forum.inductiveautomation.com/u/brians.laptop)\
**Post date:** [January 2, 2024, 8:08pm UTC](https://forum.inductiveautomation.com/t/report-unused-tags/83711/1 "2024-01-02T20:08:58Z")

</div>

I made some big changes in the PLC program, and sometime soon I have to sort through the  
"For Provider [edge] tags" and remove the obsolete tags. These tags were brought in in mass at the beginning as a way to accomplish an assembly-line type of construction. Some ended up being used, and a bunch have not been used. I'm still getting familiar with Ignition. Is there a easy way to quickly distinguish which tags have not been used on any screens?

Ignition Edge: Vision

---

<div class="post-metadata">

**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\
**Post date:** [January 2, 2024, 10:47pm UTC](https://forum.inductiveautomation.com/t/report-unused-tags/83711/2 "2024-01-02T22:47:44Z")

</div>

Assuming all used tags have good quality and unused tags (being removed from the PLC) have bad quality, I would use the tag report tool.

[https://docs.inductiveautomation.com/display/DOC81/Tag+Report+Tool](https://docs.inductiveautomation.com/display/DOC81/Tag+Report+Tool)

If unused tags are still in the PLC and/or have good quality, then you can try the tag reference tracker option, available since 8.1.34.

[https://docs.inductiveautomation.com/display/DOC81/Tag+Diagnostics#TagDiagnostics-TagReferenceTracker](https://docs.inductiveautomation.com/display/DOC81/Tag+Diagnostics#TagDiagnostics-TagReferenceTracker)

---

<div class="post-metadata">

**Author:** ![chandler](https://avatars.discourse-cdn.com/v4/letter/c/e9a140/32.png) [@chandler](https://forum.inductiveautomation.com/u/chandler)\
**Post date:** [January 4, 2024, 12:06am UTC](https://forum.inductiveautomation.com/t/report-unused-tags/83711/3 "2024-01-04T00:06:04Z")

</div>

If you have scripts that read or write to tags using dynamically created tag paths, then they probably won't show up using a tool such as the tag reference tracker. If you aren't doing anything like that, you don't have anything to worry about, but it is something to keep in mind.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [January 4, 2024, 12:22am UTC](https://forum.inductiveautomation.com/t/report-unused-tags/83711/4 "2024-01-04T00:22:38Z")

</div>

> [@chandler](#):
>
> If you have scripts that read or write to tags using dynamically created tag paths, then they probably won't show up using a tool such as the tag reference tracker

That's explicitly what the tag reference tracker is for.  
The tag _report_ tool won't be able to statically analyze complex references, but the tag reference tracker deliberately works "backwards" - every usage of a tag is "bookmarked" with as much identifying context as we can provide. For Vision clients in particular, that's not much, but you will at least be able to tell whether a given tag is _ever_ used.

---

<div class="post-metadata">

**Author:** ![chandler](https://avatars.discourse-cdn.com/v4/letter/c/e9a140/32.png) [@chandler](https://forum.inductiveautomation.com/u/chandler)\
**Post date:** [January 4, 2024, 12:23am UTC](https://forum.inductiveautomation.com/t/report-unused-tags/83711/5 "2024-01-04T00:23:54Z")

</div>

I stand corrected. Could be very useful in projects that use a lot of scripting.
