# 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:** 1\ **Showing post:** 16
**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. --- _[View the full topic](https://forum.inductiveautomation.com/t/upgrade-to-ignition-8-0-13-invalid-configuration-type-hierarchy-for-node-message/35482)._