Two instances of SOGoUserProfile are created in memory for the same database row. In the case where the row does not exist, each instance will be marked as new. If both settings and defaults are synchronized during the same request for the first time, the second insert will fail because the first will already have created the row.

A possible solution is to create the row immediately when the SELECT returns no corresponding row, forcing all subsequent writes to be UPDATE operations.