A few more users were running into the problem. It seems POTMsgSet._setTranslation wasn't setting flush orders when clearing a "current" flag on one message to make room for another. So sometimes the two may get flushed in the wrong order, and so violate the unique constraint.
A few more users were running into the problem. It seems POTMsgSet. _setTranslation wasn't setting flush orders when clearing a "current" flag on one message to make room for another. So sometimes the two may get flushed in the wrong order, and so violate the unique constraint.