The error above causes user to have to re-login to cloud timesheets multiple times throughout the day.
Currently, we have designed the access token to have a lifespan of 1 hour. We attempt to refresh the token when it reaches 80% of its expiration time, approximately 48 minutes. This process works seamlessly as long as the user's browser remains active.
However, if the user performs an action that hinders the refresh, such as putting their device to sleep, they will not receive a new token. This can lead to situations where the timeout appears to be very brief and the user will have to authenticate again.