Node Bounds incorrectly calculated on NodeGraph refresh

Video of issue:

Huge switch statements or large nodes often cause this, even default engine ones. While only a minor issue it can be pretty annoying…

Yea its really annoying could be a problem in the future…

Hello ,

I was able to reproduce this issue on our end. I have written up a report (UE-32947) and I have submitted it to the developers for further consideration. I will provide updates with any pertinent information as it becomes available. Thank you for your time and information.

Make it a great day