From what I see in the logs, one of the requests for getSession fails with an invalid authentication token (and the HTML page is the ConnectNow login page that has sneaked in because of a redirect when instead I should have returned an authentication error)We have found a problem that may be the cause of this. The current authentication system, once in a while, is slow at propagating the authentication tokens between servers so what we think is happening is that you create the authentication tok...

Your external authentication token is valid for the duration of a room session (i.e. from room start to room end).If you room restart because of a failure (server fails and your room bounces to a different server) that's not considered a new session and the authentication tokens remain valid.