# \[BUG\]Changing Path to UDT Breaks Unrelated UDT Links

**URL:** <https://forum.inductiveautomation.com/t/bug-changing-path-to-udt-breaks-unrelated-udt-links/76554>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [July 18, 2023, 9:02pm UTC](https://forum.inductiveautomation.com/t/bug-changing-path-to-udt-breaks-unrelated-udt-links/76554 "2023-07-18T21:02:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\
**Post date:** [July 18, 2023, 9:02pm UTC](https://forum.inductiveautomation.com/t/bug-changing-path-to-udt-breaks-unrelated-udt-links/76554/1 "2023-07-18T21:02:10Z")

</div>

I created a new sub-folder for my UDTs and moved a couple UDTs. After performing the move, of course I was expecting to have to update the UDT path for the affected UDTs. However, every UDT that exists in my tag provider shows a configuration error, even though when I open the UDT instance definition it points to the correct UDT path.

To resolve, I've been adding an "s" to the end of the path, apply the changes, then remove the "s" and apply changes again. This makes the configuration error go away, but I did not expect this to affect other UDTs that are completely unrelated to the ones that moved.

(8.1.27)

---

<div class="post-metadata">

**Author:** ![amarks](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarks/32/45610_2.png) [@amarks](https://forum.inductiveautomation.com/u/amarks)\
**Post date:** [July 18, 2023, 9:06pm UTC](https://forum.inductiveautomation.com/t/bug-changing-path-to-udt-breaks-unrelated-udt-links/76554/2 "2023-07-18T21:06:18Z")

</div>

This resolves itself after restarting the gateway