# \[Solved\] Need help with system.tag.browse and diagnostic tool - Bit State Change Locator

**URL:** <https://forum.inductiveautomation.com/t/solved-need-help-with-system-tag-browse-and-diagnostic-tool-bit-state-change-locator/28371>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [September 19, 2019, 5:47am UTC](https://forum.inductiveautomation.com/t/solved-need-help-with-system-tag-browse-and-diagnostic-tool-bit-state-change-locator/28371 "2019-09-19T05:47:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Sanderd17](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sanderd17/32/8735_2.png) [@Sanderd17](https://forum.inductiveautomation.com/u/Sanderd17)\
**Post date:** [September 19, 2019, 5:58am UTC](https://forum.inductiveautomation.com/t/solved-need-help-with-system-tag-browse-and-diagnostic-tool-bit-state-change-locator/28371/2 "2019-09-19T05:58:44Z")

</div>

So, if I'm right, you intend to use it to log effects inside the PLC when a certain trigger happens (like a something passes before a photocell).

That can indeed be a very handy tool. Thanks for sharing.

> [@kpswiney](#):
>
> I understand the dangers of recursively searching through folders, but here it necessary. Is there a safer way to go about this recursive search and query?

Although it's bad practice to use this in an operator screen (locking up the interface for an operator will cause frustration), it's not such a big issue if you do it for diagnostics, and only technical people are supposed to use it.

---

_[View the full topic](https://forum.inductiveautomation.com/t/solved-need-help-with-system-tag-browse-and-diagnostic-tool-bit-state-change-locator/28371)._