The API key used is not one of a premium user so when a registered premium user solve a premium challenge the bot get a 401 5 time and go idle, there is currently no dynamic workaround.
First we should use a premium API key but still the bot should be able to handle 401s
The API key used is not one of a premium user so when a registered premium user solve a premium challenge the bot get a 401 5 time and go idle, there is currently no dynamic workaround.
First we should use a premium API key but still the bot should be able to handle 401s