Hi @aahulsebos – it seems to me that your patch update from 5.0.0 to 5.0.1 may have fixed this problem. I am not seeing it since updating.
Edit: I needed to install the Complianz update then clear all cookies, localstorage and sessionstorage, but since then the error has not recurred.
-
This reply was modified 3 years, 10 months ago by hdsteve.