I have the same issue, filed a ticket ( 78478 ) for this last Tuesday.
Our case was slightly different:
> Case object has an 1-1 association with WorkItem, the work item is like a task, each case has at least one task, showing the current "state" of the case. While committing the Case object the ConnectionBus_Update logs: EntityStorer: Incoming StoreRequest: ObjectStoreRequest type: INSERT INTO ....WorkItem
While this object already exists and the MF has not yet reached the step where the WorkItem is updated. This INSERT INTO is incorrect (not modelled) and should not occur because the object already exists, thus causing the duplicate key value unique constraint error
Edit: first noticed this error in 7.21.0 but also occurs in 7.22.1
I've noticed a similar error in my log. Mendix version 7.21.0
I haven't looked into it yet. But the error gets thrown when I change a DateTime attribute on an already committed object and then commit the object again.
Same error here with Mendix version 7.22.2.
Is there an update on this?