@juanshishido
Sorry for my delay. I hadn’t noticed that anyone finally replied.
No, we haven’t solved the problem, but I also haven’t looked at it in quite some time either. We’ve just been working around it by never trying to update the timesTomorrow, I’ll look to repro it and get you the details