We are aware that this is a major issue, but unfortunately it would be extremely complex to fix. It is properly logged and we will possibly attempt to fix it at some point, but can't provide any time frame, sorry.