Performing a hot reload after updating an Enum will not reflect the update until the editor is closed/reopened.
Restarting the editor dose not immediately update the enum. When the editor is restarted, it will treat the Enum as a Byte instead of Enum. If a custom enum is updated/hot reloaded, associated blueprint nodes need to be replaced.
Compiling the code with the editor closed (rather than preform a hot reload) will update the existing nodes properly.
The Enum node added in step 6 still only has two options after adding a third in code. Restarting the editor will update the Enum and show the third option.
Triggering hot reload updates code based Enums
Head over to the existingAnswerHub thread and let us know what's up.