HiI had this issue when I was trying to modify an existing Fragment that was being used in a Journey. As a workaround I created a new version of the Fragment and updated the Template-Email-Journey to use itIf you logged this as a bug I'd be interested to know if Adobe had a differernt solution