Best Answer Christopher (Drashna) , 19 April 2017 - 07:35 PM
The 429 response code is a throttling response.
This means that there isn't anything we can really do. We do automatically retry when we get these sort of errors, and we back off exponentially (eg, wait longer and longer to retry).
But basically, Amazon's servers are actively refusing to return the data that we're requesting. There is no fix or work around here, because this is ENTIRELY a server side issue. It's not an issue with our software (especially as we're not the only ones experiencing this issue. RCLONE and other cloud utilites are seeing this with Amazon Cloud Drive.
THis is likely due to Amazon's servers getting "hammered" and them not able to keep up with the requests. Which means this is an infrastructure issue.... or "a consequence of using a consumer grade cloud provider" (which is a shitty response....).
This has happened a couple of times in the last couple months, and usually this clears up in a couple of days. It's a shitty situation, as "waiting" is a horrible response. But we're completely at Amazon's mercy here.
It's issues like this, is why the Amazon Cloud Drive provider is considered an experimental provider.
Hopefully, if they re-approve us for production status, this will stop occurring, but I seriously doubt that (RCLONE and the like *are* approved, IIRC).Go to the full post