TheNetsky
The "Too Many Requests" Freeze on Chrome need an auto Refresh to fix that
Hello
i noticed that after 3rd/4th account, this comes just after login, and when you refresh it 2/3 times manually, it goes and bot continue the work, happens on desktop and mobile tasks need to add an auto refresh if this happens to fix it
I've never had this happen to me personally, however I only use one account for this.
I also have this problem for newly created account
those accs are created 2 years ago lel
I guess this has something to do with reloading the 1st page to refresh the dashboard data, however I also seen people with more accounts not having this issue. This is as far as I know the first time anyone posted about this. However if you can send me the HTML you receive from this I can look into a refresh method once this page happens, since you said refreshing the page fixed this correct?
I have this problem aswell and I think good fix is if script doesn't get logs for long time it just reset and put it in config like https://github.com/TheNetsky/Microsoft-Rewards-Script/pull/118 but more updated as this were made quite long time ago and a lot have change in the script. As well potential reson for this might be that when a lot accounts going on the script doesn't close fully old chromium and you can see them in taskmanager and after time like 5 account there like 15 chromium, which might create some kind overpacking to chrome which creates this issue
but my problem is a bit different to screen shot as mine just doesn't load pages at all like forever try to load pages
Hello
i noticed that after 3rd/4th account, this comes just after login, and when you refresh it 2/3 times manually, it goes and bot continue the work, happens on desktop and mobile tasks need to add an auto refresh if this happens to fix it
This might be aswell because of bad proxies or overloaded ip
In my case refresh didn't work, i waited till next day to try again and got following message
i added recovery mail and successfully logged in with otp via mail. after saving session it worked fine next time.
( The accounts that are having issues are all my newly created accounts that have no recovery information added, the old accounts that have recovery information work fine for me.)
Yeah, this error is weird. Microsoft probably added some new security. If you are normally using a proxy, do a batch whitout a proxy. Unless your personal IP is flagged, you won't have the error, and the script will keep the cookie, so that when you start up with your proxy, you will directly be connected to your account even if the ip is sus.
