7 Replies
seeing it again today
I just managed to fix it for one particular user by manually removing and reassigning all of their roles
I dont think all roles changing made a difference. But a single role could already affect it as it might then cause the cache to be loaded
I typically fix this issue by kicking them from the queue, having them reclaim, then bumping them back to where they were.
But that only works if I know who the “unknown user” is
we have a change for this in the next deployment
unfortunately, for my test bot, it's only in 2 servers and everything is always in cache so it is quite hard to proper test
but hopefully it will improve
expectation would be to only see unknown users in the respawn history
the 5.1.3 version has been deployed and also had the changes above
hopefully it has improved, if you have feedback, let me know
I haven’t seen anything yet but it wasn’t a common occurrence previously