# Error Moving Tag into a folder

**URL:** <https://forum.inductiveautomation.com/t/error-moving-tag-into-a-folder/108555>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [July 16, 2025, 2:03pm UTC](https://forum.inductiveautomation.com/t/error-moving-tag-into-a-folder/108555 "2025-07-16T14:03:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan\_Craig](https://avatars.discourse-cdn.com/v4/letter/r/45deac/32.png) [@Ryan\_Craig](https://forum.inductiveautomation.com/u/Ryan_Craig)\
**Post date:** [July 16, 2025, 2:03pm UTC](https://forum.inductiveautomation.com/t/error-moving-tag-into-a-folder/108555/1 "2025-07-16T14:03:37Z")

</div>

I currently have a folder in the tag browser with a lot of tags in it.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/d/dde7129474ae7c47d59f6a3ee38513fda6aab2af.png)

I recently added a new tag that I want to put within the folder but every time I try, I get this error:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/7/17bf2347f592da4df7d6eb4969dbde985ed45812.png)

Even though the folder already has tags in it. Is it because the folder is apart of a UDT?

Any idea what could be causing this?

---

<div class="post-metadata">

**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\
**Post date:** [July 16, 2025, 2:21pm UTC](https://forum.inductiveautomation.com/t/error-moving-tag-into-a-folder/108555/2 "2025-07-16T14:21:51Z")

</div>

Yes, thats not a folder, but a tag instance of a UDT type. If you need to add an additional element, modify the UDT.

---

<div class="post-metadata">

**Author:** ![Ryan\_Craig](https://avatars.discourse-cdn.com/v4/letter/r/45deac/32.png) [@Ryan\_Craig](https://forum.inductiveautomation.com/u/Ryan_Craig)\
**Post date:** [July 16, 2025, 2:23pm UTC](https://forum.inductiveautomation.com/t/error-moving-tag-into-a-folder/108555/3 "2025-07-16T14:23:02Z")

</div>

Ok, just needed to confirm that was the issue. Thanks for the help.
