This is an interesting error! I’m currently installing a fresh 5.4.1 instance to verify reproduction steps on my side assuming this is a bug introduced in 5.4.1. Since this only affects the LevelBlueprint, can the reference be assigned outside of the LevelBP? (Not meant to be a workaround, but can help determine where the fault is).