Transaction completion process is slowed down by multiple UPDATE queries on ITM_ITEM_DIMENSION_VALUE
Hi, community,
We experienced a delay in the completion of the transaction. So when I checked the logs I found out there were about 330 update queries run on ITM_ITEM_DIMENSION_VALUE and a few on ITM_ITEM_DIMENSION_TYPE after PersistCurrentTransactionWorker.
The updates are changing nothing but update_user_id and update_date, so it seems unnecessary or a base bug. It is concerning to us because sometimes it leads users to click the complete transaction button multiple times, which invites PK errors.
So regarding this, I have a few questions.
- Do you believe this is the base bug?