Can confirm that, as I’ve had it happen again by accident.
Doubtful it’ll be fixed anytime soon, but at least now I have found a way to proceed:
- Roll back to a previous working version of the Blueprint.
- Open the editor.
- While in-editor, update to the latest version of the Blueprint.
- Fix the offending Blueprint and resave it.
- Restart the editor.