# ManagedTagProvider queries

**URL:** <https://forum.inductiveautomation.com/t/managedtagprovider-queries/114105>\
**Category:** Module Development\
**Tags:** ignition83\
**Created:** [February 21, 2026, 9:05am UTC](https://forum.inductiveautomation.com/t/managedtagprovider-queries/114105 "2026-02-21T09:05:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\
**Post date:** [February 21, 2026, 9:05am UTC](https://forum.inductiveautomation.com/t/managedtagprovider-queries/114105/1 "2026-02-21T09:05:39Z")

</div>

![Screenshot 2026-02-21 at 19.57.03](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/1/c17fe8f96460d5875c2779df860d474ab8c5aa4b.png)  
I am trying to use a Managed Tag Provider, the provider works nicely besides one element.  
If I try and make a tag that is the same path as an existing tag folder, I get this log error from the gateway.  
I understand why it appears, but there seems to be no way to query the ManagedTagProvider to find if there is an existing folder at that path before using `.updateValue()` and thereby triggering the pictured gateway log. I want it to fail to update, but its flooding the logs massively.

Is there any way around this besides tracking the tag paths externally to the ManagedTagProvider?