Update: If you are on Domino version 4.6.2, please reach out to support if you see the error below. This likely indicates an issue that will need to be investigated. For all other versions of Domino the article below still applies.
In some deployments you may regularly the following in the workspace/run logs:
ERROR:__main__:Attempt to refresh failed due to an HTTP Error
HTTP Error 400: Bad Request POSTing to http://keycloak-http.domino-platform-
Though it looks worrisome, this is a benign message and can be ignored.
Usually we see this "Bad Request" because the authentication token used to initiate a run/workspace is no longer valid. Most of the time this occurs when users log out, then log back in, requiring a new access token to be issued. Logging in will invalidate the previous access token, but the user's new token will grant the same level of access. Besides the above message, there will be no impact on how Domino works when users log out and login repeatedly.
Another variation on this is the following:
INFO:__main__:-- Refreshing access token --
Users will see this in their workspace/run logs indicating their access token is about to expire so the system is retrieving a new one. This is also nothing to be concerned about and indicates the system is working as expected. Token timeout period will vary by deployment and is set by local admins (default every 6 minutes).