# \[Warning in Logs\]internaljson

**URL:** <https://forum.inductiveautomation.com/t/warning-in-logs-internaljson/39766>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [October 16, 2020, 7:03pm UTC](https://forum.inductiveautomation.com/t/warning-in-logs-internaljson/39766 "2020-10-16T19:03:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kenny.tucker](https://avatars.discourse-cdn.com/v4/letter/k/e19adc/32.png) [@kenny.tucker](https://forum.inductiveautomation.com/u/kenny.tucker)\
**Post date:** [October 16, 2020, 7:03pm UTC](https://forum.inductiveautomation.com/t/warning-in-logs-internaljson/39766/1 "2020-10-16T19:03:43Z")

</div>

v8.0.13. Our logs are LOADED with warnings like so:

“Invalid configuration type heirarchy for node ‘0d64455e-2a7f-460a-ae78-c058a2d2ac6a.fc220902-30e3-466b-acac-ae8e54ea2c0b’. Parent entity ‘0d64455e-2a7f-460a-ae78-c058a2d2ac6a’ was not found, or not loaded in the correct order.”

Any ideas what this is from? There are 21 of these warnings that occur every 10 seconds.

---

<div class="post-metadata">

**Author:** ![mgross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mgross/32/3311_2.png) [@mgross](https://forum.inductiveautomation.com/u/mgross)\
**Post date:** [October 16, 2020, 8:21pm UTC](https://forum.inductiveautomation.com/t/warning-in-logs-internaljson/39766/2 "2020-10-16T20:21:09Z")

</div>

Best guess is that a UDT was deleted at some point. But figuring out which one is really painful without digging thru the internal database. Your best bet is to contact IA Support and be prepared to hand over a tag export or a gateway backup. They should be able to untangle it or at least offer some idea of what is missing.

---

<div class="post-metadata">

**Author:** ![kenny.tucker](https://avatars.discourse-cdn.com/v4/letter/k/e19adc/32.png) [@kenny.tucker](https://forum.inductiveautomation.com/u/kenny.tucker)\
**Post date:** [October 20, 2020, 6:25pm UTC](https://forum.inductiveautomation.com/t/warning-in-logs-internaljson/39766/3 "2020-10-20T18:25:37Z")

</div>

Issue ended up being related to the Backup Gateway. The synchronization status was out of date. Resolved by rebooting each gateway, changing the mode from Master to Independent and back to Master. This allowed the sync status to fully update.