As @Tavikron mentioned, sometimes, selecting an instance while currently selecting a different class of instance in the explorer causes this bug. This is not GUI specific and can occur for all classes. As a workaround, it’s worth noting that selecting the exact instance that triggered the issue and then selecting the desired instance again fixes this issue until a different case of it occurs.