As a faster workaround, I hit RefreshNode on “bugged” nodes and compile BP!
Same problem happens to me when I hotreload so I tend not to use hotreload anymore when working on this particular BP (containing “bugged” enum).
Problem might be related to creating a BP with an enum (defined in C++ in my case) UPROPERTY and then changing (adding/removing/inserting/renaming?) values in enum afterwards. Not sure about all exact causes for this bug but maybe it will help to track it down completely…
My version is: 4.8.2
I had also that kind of warnings when starting editor so I decided to recreate “bugged” BP from scratch (and without modifying enum in C++ anymore)…
LogEnum:Warning: Enum Text OldEnumValue for Enum EMyActorState failed to resolve to any value