Is it possible to throw an error in blueprint?

I think that workaround is not working anymore. That trick was probably leveraging a bug of the SetOwner functions which has probably been fixed.