02.03.2019, 14:24
(This post was last modified: 02.03.2019, 14:25 by Erwin van der Zwart.)
Hi,
Custom JS is never executed on the server side, it’s just a piece of JS that is injected into the HTML that is loaded by the client(s) and executed by the browser. So it runs always client side.
Once loaded by the browser it should always execute and cache has nothing to do with that, check the HTML source code if it’s inserted correctly, then it should work every time it’s triggered.
Only reason that might not trigger it after being loaded is a interupted websocket but that would also stop all other object updates.
BR,
Erwin
Custom JS is never executed on the server side, it’s just a piece of JS that is injected into the HTML that is loaded by the client(s) and executed by the browser. So it runs always client side.
Once loaded by the browser it should always execute and cache has nothing to do with that, check the HTML source code if it’s inserted correctly, then it should work every time it’s triggered.
Only reason that might not trigger it after being loaded is a interupted websocket but that would also stop all other object updates.
BR,
Erwin