Handle potential race conditions around notoptions
09 March 2021
16:22:52 GMT+0000
There is a possibility in the core that if a notoptions are being updated at the same time, a change could be rewritten.
This would then result in option being stored in DB but also marked as non-existing in notoptions making further attempts to add such option always fail without removing the options from the list of non-existing options.
We have deployed a fix for this over a week ago but decided to do 2 phase deployment. The first phase was all non-prod environments. As we did not see any negative effects of this change we will roll it out to prod environments with this change.