Anyone can help ????? We are running after this since quite a lot now. We thought it was something related with the browser cache but we did not manage to understand the real root cause. We tried different browser, same behaviour. Chrome | Firefox have similar statistic on the error. Running the browse in the server where SPLUNK runs seems to reduce the statistic of the error occurrence.