I'm out of ideas. Obviously this shouldn't be occurring. The simplest solution would be to delete the node and re-add it again but that's far from ideal. Failing that as an option I suggest opening a case with support so we can look through the diagnostics to determine why the child status indicator isn't being properly updated.
↧