Hi,
If you would operate on CU11 this behavior might be caused by a bug for which a hotfix has been released. But since you are working with CU12 this hotfix should already been included.
You mention that the error comes up some time.
Can you specify what some time means? Can you try to identify a specific Transaction/item that triggers this message?
Can you replicate this issue in a demo/test Environment?
Best regards,
Ludwig
