hello ,my company (Cloudsfder) are doing data migration for customer from goolge derive to dropbox , 5 TB ,
we are getting weird behavior when creating some of the folders- the request just returning null,
and if i retry sometimes it is work and sometimes still getting null,
this is very weird
I'll be happy to help with any issues you're having with the Dropbox API, but I'll need some more information. Please reply with:
Official Dropbox .Net v2 SDK
app key :jbei6w7fwpgrzgq
app key business : li4q7wb8ayguxmy
the steps are only call create folder,
but we are migrating 5 Tb so we are making many request -maybe we hit a rate limit? but no response only null.
not event an error just a null response
Please share the actual code and show whatever result/response you are getting so we can look into it and try to reproduce the issue. For instance, if you're inspecting the actual HTTPS response, please show the whole thing, including headers, or if you're using a native method in the SDK like mentioned above, please show what type and value it is returning or raising. Thanks!
Client.AsMember(request.AsMember).Files.CreateFolderV2Async(prefix + name)
this is the actual request from the SDK I am using.
and I am not getting any response only null, that is why this is so weird
Can you clarify what you mean when you say you are only getting "null"? Is that the value being returned by the CreateFolderV2Async method itself, or is the method raising an exception?
Also, the code you shared here does not show you retrieving the return value, nor handling any exceptions. Additionally, CreateFolderV2Async is an async method, but you don't seem to be awaiting it or checking the result, at least in the code you shared here. And, what is the type "request" object in this code?
Please share the full relevant code and output so we can understand the issue in context in order to investigate and offer help.
If there are multiple changes at the same time in the same account or shared folder (or more accurately, "namespace"), you can run in to this 'too_many_write_operations' error, which is "lock contention". That's not explicit rate limiting, but rather a result of how Dropbox works on the back-end. This is a technical inability to make a modification in the account or shared folder at the time of the API call. This error indicates that there was simultaneous activity in the account or shared/team folder preventing your app from making the state-modifying call (e.g., adding, editing, moving, copying, sharing, or deleting files/folders) it is attempting. The simultaneous activity could be coming from your app itself, or elsewhere, e.g., from the user's desktop client. It can come from the same user, or another member of a shared folder. You can find more information about lock contention here.
The app should be written to automatically handle this error when it occurs, but to help avoid this error to begin with, you should avoid making multiple concurrent state modifications in the same namespace and use batch endpoints where possible, such as CreateFolderBatchAsync. That won't guarantee that you won't run in to this error though, as contention can still come from other sources, so you should also implement error handling and automatic retrying as needed.
The way we work is changing. Share and discover new ways to work smarter with Dropbox in our community.Sound good? Let's get started.
For more info on available support options, see this article.
If you found the answer to your question, please 'like' the post to say thanks to the user!