Had a call with Danilo who explained to me that it's because the email address table is now replicated into the master store from a separate store.
The stack trace is misleading because it appears to be caused by a "find" which is not modifying anything, but the find also does a flush which will cause it to try and write a different record. We need to find out what it's trying to modify and get that object from the right store.
Had a call with Danilo who explained to me that it's because the email address table is now replicated into the master store from a separate store.
The stack trace is misleading because it appears to be caused by a "find" which is not modifying anything, but the find also does a flush which will cause it to try and write a different record. We need to find out what it's trying to modify and get that object from the right store.