Dear all

looking for IFS Cloud Timeclock users who can help me understand why they constantly go “offline” in the sense that the token fails to get renewed and they appear offline. Only a browser cache clear and login again resolves the issue. Having 15 around the world, this happens very frequently, and more frequently since upgrading to 24R2.

In the browser network logs we see the regular GetServerTime() every minute, and a Post token every 5 minutes where it gets a new token (also seems to create a new session in IFS rather that reusing the existing one, and rather than using refresh tokens).

Once in a while, completely random, that token refresh fails, with a 504, after which the clock becomes completely unusable, and only a clear cache helps.

Any help appreciated, IFS claims non-reproduceable so far, though we have it with any browser, and client, within our network, from outside. Only thing we are not sure is our Citrix ADC reverse proxy, and have not identified where the 504 comes from.