You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
ServiceUnavailable 503 when doing a lot of requests - expected rate limit error
When there are a lot of requests to the API, at some point a 503 - ServiceUnavailable error code is returned. The documentation does not cover this case (https://developers.dropbox.com/error-handling...
Greg-DB
Dropbox Staff
Dropbox StaffDropbox does currently use 429 for explicit rate limiting, but there are a number of different error cases, some of which may return a 500 or 503. (The way these were handled has changed somewhat over the years and across API versions.)
In any case that you get a 5xx (such as 500 or 503), retrying the request after a short delay, with an exponential backoff as you mentioned, is a good way to handle these.
Thanks for the confirmation. I think it would be great if this information could be added to the API's "error handling guide", which already covers other HTTP result codes, but not this one. Judging by the amount of posts here in the forums, the 503 code is confusing many developers
- Greg-DB
Thanks for the feedback!
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
