If it's one off, they may have seen the repository shifting from one node to another in our server cluster. The sessions are reset and there is a little bit of unavailability while the repository is initialized on another node. If it's more common than that, I would suggest opening a support case with the names of the users, the application they were in and an approximate time when they were asked to log in again.