jsayago22

Hi, we already updated to version 4.1.6.2 and the error is still there. We don’t know on wich page the error occurs but the log monitor shows that error.