I actually had the same problem in one of my instances. I’m following the thread for any solutions for troubleshooting.
However, for one of the instances that we had experienced this, it was when we were implementing the 2.37.4 version and some versions have this issue so what I can recommend you try first is ensuring you have the latest version of 2.37 which is 2.37.8