Sometimes by accident or by a third party supplier, the locale of the method server is changed
On our case it was because of a third party supplier, we were able to find out thanks to this extra debug trace that would throw a "dummy" error to print to stacktrace and find out who is calling the method setLocale of WTContext
Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.
Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.
I would be surprised if anyone do, it is a change that would help your development team mostly, they were the ones who asked me to create the idea, but if I were them I would add this change straight away to find out what is changing the locale immediatelly
