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
500 internal Server Error https://api.dropboxapi.com/2/files/list_folder/continue
I've using the following endpoint to retrieve files and folders:
https://api.dropboxapi.com/2/files/list_folder this returns 2000 entries and then get hasmore = true and the cursor. I then user th...
Greg-DB
Dropbox Staff
Dropbox StaffHi sfbrad, no, there's no entry limit for a cursor. This error just indicates something happened to go wrong for that particular call. If you share a X-Dropbox-Request-Id response header value, I can look this up for you.
Thanks for the reply.
X-Dropbox-Request-Id: 7c19057695051c5944f59c0644e3ae1a
X-Dropbox-Request-Id: 7c19057695051c5944f59c0644e3ae1a
- Greg-DBThanks! That's helpful. That's the same issue as reported by thedeck earlier in this thread. I'll follow up here once I have an update.
Hi,
Is there any update to the orginal post made by Cynthia back in August last year? I have been asked to follow up on this?
Thanks
- Greg-DBThe team has been working to resolve these issues, but the error rate is still non-zero.
These multiple issues appear identically to the API client though, so if you need us to check on a specific issue, please open a ticket with a new X-Dropbox-Request-Id value:
https://www.dropbox.com/developers/contact
- Greg-DB
Regarding the errors reporting by thedeck and sfbrad, these 500s can be caused by certain file metadata not being available yet, at the time of the API call. The team has been working on improvements around this. When this information is still not available, Dropbox will now be returning 429s, to instruct the app to call back later, when the metadata will be available.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
