Thank you very much for your feedback, @satoko!
It's been fixed but still temporarily, to be honest. Our engineer has still been checking all the code and trying to find the exact cause, trying to fix it once and for all.
I'm sorry, but if you see the problem again, please feel free to tell us.
Thank you very much for your understanding!