I’ve seen this before when adding a blueprint accessible function/property to an object that is already referenced in an existing blueprint. The only work-around I’ve found is to simply tell it to not save and re-launch the editor, at which point you can have it restore the work in progress if needed and it will then save properly. Really annoying.