This is an improvement regarding the update made on issue EZP-20537
When the sync failed on "content update" it should try to do a create action "content create", this was the implemented UPSERT strategy.
However this might bring some inconsistency and therefore it should throw a visible warning/notice or any other kind of visible info for the user that a update failed and a create was made instead.