# \[BUG\]PSA: Nested UDTs can be TOO Nested!

**URL:** <https://forum.inductiveautomation.com/t/bug-psa-nested-udts-can-be-too-nested/83288>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [December 18, 2023, 10:12pm UTC](https://forum.inductiveautomation.com/t/bug-psa-nested-udts-can-be-too-nested/83288 "2023-12-18T22:12:16Z")\
**Posts on this page:** 1\
**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:** [December 18, 2023, 10:12pm UTC](https://forum.inductiveautomation.com/t/bug-psa-nested-udts-can-be-too-nested/83288/1 "2023-12-18T22:12:16Z")

</div>

I have a UDT that contains an instance of a "SubUDT" who's definition is inherited from a UDT that's inherited from a UDT... so on.

i.e. path to this UDT instance is

```auto
UDT / SubUDT_Instance < UDT_Parent1 < UDT_Parent2 < UDT_Parent3 < UDT_Parent4

```

What has happened here is that updates to the definition of this UDT do not automatically populate to instances of the UDT. If a new instance (exact replica, just created after the definition is updated) is created, this instance is updated, and can even coexist with the outdated instance.

I have verified this behavior with support and I am not aware of a workaround at the moment, other than restart each instance of the UDT (you can also restart the parent folder that holds the instance).