Integer to enum(byte) with strange casting result

Thanks for reply. That would be great to be able to track bugs.
Regarding your comment on this being fixed in 4.9, it doesn’t really make sense.

This is a major issue as it means no project using blueprints can continue using ENUMS until this issue is fixed. Am I missing a work around? (other than converting all enums to INTs)