While making sure the upgrade-0.42 command was working as expected to upgrade from 0.41 to 0.42, we've detected that the standardId of the new bodyV2 (type RICH_TEXT_V2) was not properly set ; standardId was not correct. This was forcing the sync-metadata command to try to re-create the field again.