# Upgrade to ignition 8.0.13 : Invalid configuration type hierarchy for node message? **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [June 10, 2020, 7:52am UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482 "2020-06-10T07:52:08Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [June 10, 2020, 7:52am UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/1 "2020-06-10T07:52:08Z")
I’ve upgraded a **8.0.12 gateway to 8.0.13** , I have some message: ```auto INFO | jvm 1 | 2020/06/10 09:50:04 | W [t.s.internaljson] [07:50:04]: Invalid configuration type hierarchy for node '02dce1a3-f032-4a9c-bf4e-09ed73168aee.f8cc51fc-8062-4adc-8109-37c248ac3920'. Parent entity '02dce1a3-f032-4a9c-bf4e-09ed73168aee' was not found, or not loaded in the correct order. provider=default ``` what does it means ? ---
**Author:** ![adam.todorski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/adam.todorski/32/19388_2.png) [@adam.todorski](https://forum.inductiveautomation.com/u/adam.todorski)\ **Post date:** [September 2, 2020, 1:55pm UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/2 "2020-09-02T13:55:43Z")
I’ve seen the same thing on 8.0.12 with a cold redundancy pair, the errors stop when the cold standby node is shut down. No idea what the problem is (yet). ---
**Author:** ![nicholas](https://avatars.discourse-cdn.com/v4/letter/n/4da419/32.png) [@nicholas](https://forum.inductiveautomation.com/u/nicholas)\ **Post date:** [November 8, 2020, 1:34pm UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/3 "2020-11-08T13:34:34Z")
I am getting the same problem in 8.0.16, but they are constantly pouring in every second and flooding out useful messages. So, I am just blocking them by setting the logger level for this internaljson to error: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/a/9ad568440dafe20f3658c6db492f3f622810afd9.png) ---
**Author:** ![james\_electriceng](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@james\_electriceng](https://forum.inductiveautomation.com/u/james_electriceng)\ **Post date:** [March 15, 2021, 4:43am UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/4 "2021-03-15T04:43:34Z")
I am getting the same error. Has anyone found out a solution to this problem yet? I’m using 8.1.3. ---
**Author:** ![yin.cheng](https://avatars.discourse-cdn.com/v4/letter/y/85f322/32.png) [@yin.cheng](https://forum.inductiveautomation.com/u/yin.cheng)\ **Post date:** [February 15, 2023, 9:23am UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/5 "2023-02-15T09:23:28Z")
I am getting this error as well.. I am using edge 8.1.7 ---
**Author:** ![joshdunstan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/joshdunstan/32/43306_2.png) [@joshdunstan](https://forum.inductiveautomation.com/u/joshdunstan)\ **Post date:** [May 18, 2023, 12:26am UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/6 "2023-05-18T00:26:06Z")
Anyone get anywhere with this? I'm seeing it on 8.1.17 ---
**Author:** ![glenfry1](https://avatars.discourse-cdn.com/v4/letter/g/f07891/32.png) [@glenfry1](https://forum.inductiveautomation.com/u/glenfry1)\ **Post date:** [May 19, 2023, 7:39pm UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/7 "2023-05-19T19:39:55Z")
Hey Josh, shoot me email to me to support@icontrols.com.au. Have a feeling our support team may have seen this on a call a few months back. ---
**Author:** ![Daniel\_Kareem\_Tabet](https://avatars.discourse-cdn.com/v4/letter/d/4da419/32.png) [@Daniel\_Kareem\_Tabet](https://forum.inductiveautomation.com/u/Daniel_Kareem_Tabet)\ **Post date:** [October 21, 2024, 7:44am UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/8 "2024-10-21T07:44:02Z")
Hey! Has anyone solved this yet? I am running into the same exact issue on 8.1.35 but I can't find many resources. ---
**Author:** ![denji26](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/denji26/32/5805_2.png) [@denji26](https://forum.inductiveautomation.com/u/denji26)\ **Post date:** [November 1, 2024, 6:29pm UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/9 "2024-11-01T18:29:02Z")
I also see this on 8.1.39 seemingly when the Main Gateway tries to take back over from the Backup Gateway after a failover. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/2/7256d2dbb8d4c1c502e008e1cc0d1a6053880505.png) Then floods the logs with thousands of errors. ---
**Author:** ![Drew\_Hitchcock](https://avatars.discourse-cdn.com/v4/letter/d/b5ac83/32.png) [@Drew\_Hitchcock](https://forum.inductiveautomation.com/u/Drew_Hitchcock)\ **Post date:** [January 21, 2025, 3:23pm UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/10 "2025-01-21T15:23:47Z")
Same here on 8.1.17. When I inspect, it says it's an issue with the backup gateway and references a particular tag provider. Does anyone know what causes this and how to eliminate the root issue? ---
**Author:** ![framebuilder](https://avatars.discourse-cdn.com/v4/letter/f/96bed5/32.png) [@framebuilder](https://forum.inductiveautomation.com/u/framebuilder)\ **Post date:** [February 14, 2025, 6:34pm UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/11 "2025-02-14T18:34:39Z")
Same here on 8.1.35. Redundant setup. Filling up logs. Anyone have any info on this? ---
**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\ **Post date:** [May 5, 2025, 9:15am UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/12 "2025-05-05T09:15:27Z")
I'll bump this thread as I'm having my logs filled by this. Literally the 500 hundred pages are only this. I can't see any consequences so far, except for the log flood. ---
**Author:** ![AnirudhVelamore](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@AnirudhVelamore](https://forum.inductiveautomation.com/u/AnirudhVelamore)\ **Post date:** [March 1, 2026, 3:27am UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/13 "2026-03-01T03:27:44Z")
Anyone know how to identify the “node” or the “parent entity”? I’ve taken a look at tags and UDT definitions from a high level and didn’t find anything obviously wrong. ---
**Author:** ![Porter\_Ellis](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@Porter\_Ellis](https://forum.inductiveautomation.com/u/Porter_Ellis)\ **Post date:** [May 28, 2026, 12:29pm UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/14 "2026-05-28T12:29:51Z")
This error flooded the logs so much that the gateway crashed. @pturmel, any thoughts on this one? Seems like the issue has been around for some time. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 28, 2026, 12:33pm UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/15 "2026-05-28T12:33:32Z")
I've never seen this one myself. I vaguely recall something like this in a release note. ---
**Author:** ![Steve\_Laubach](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_laubach/32/60900_2.png) [@Steve\_Laubach](https://forum.inductiveautomation.com/u/Steve_Laubach)\ **Post date:** [May 28, 2026, 12:59pm UTC](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482/16 "2026-05-28T12:59:13Z")
As some said in this thread, it seems to be linked to redundant failover. 2 other threads I think are worth checking out. > [@Redundancy's Synchronization Error](https://forum.inductiveautomation.com/t/redundancys-synchronization-error/100558): > > Hello everyone! I am trying to set the redundancy of a remote tag provider. I have the following architecture with four different machines: Main gateway, Remote Tag Provider, gateway redundant, tag provider redundant. I have set in the backup gateway, Standby Activity Level as cold. During synchronization, log throws the following messages: [t.s.internaljson] [07:16:10]: Invalid configuration type hierarchy for node 'guid number'. Parent entity 'guid number' was not found, o… An IA rep responded in this thread > [@\[Perspective\] HTTP Error 503 Service Unavailable](https://forum.inductiveautomation.com/t/perspective-http-error-503-service-unavailable/100025): > > Hello. Since we've updated to Ignition 8.1.43 we've been encountering an annoying issue. Every morning, when we start up our system, Chrome loads up with a Error 503 Service Unavailable message. The browser automatically opens after around 5 minutes pointing to the login page of our project through a Windows Scheduled Task. We've never encountered this behaviour beforehand; moreover rebooting the system apparently resolves the issue. The gateway logs show a bunch of warning like this one at t… Some of the messages indicate that it started after an upgrade on the system. If you can safely do it, I would break redundancy, upgrade both systems to the same version and then re-establish redundancy and see if it's fixed. You can also contact support and have them look at the backend db. Of course, make a gateway backup before trying this.