Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
/move_batch/check_v2 returns too_many_write_operations for some files
I use https://api.dropboxapi.com/2/files/move_batch_v2 to move files and get the `async_job_id`. Then I use https://api.dropboxapi.com/2/files/move_batch/check_v2 with `async_job_id` to check the pro...
Ok, thanks for your answer. But we send move_batch/check_v2, we receive only 'too_many_write_operations' for some files without id or name. Does it mean that I need to move all files again using 'files/move_batch_v2'? Can't we detect all the files which were failed.
Shahen wrote:... But we send move_batch/check_v2, we receive only 'too_many_write_operations' for some files without id or name. Does it mean that I need to move all files again using 'files/move_batch_v2'? ...
Hi Shahen,
Calling 2/files/move_batch/check_v2 gives you the status of a scheduled operation identified with the id provided. It doesn't matter how many times you will call this API, doesn't matter the status (in progress or completed) - it will always refers to the same operation (no new one gets launched). To initiate new move try, you have to perform 2/files/move_batch_v2 API call again, of course.
Shahen wrote:... Can't we detect all the files which were failed.
🤔That would be a good feature request. As a workaround, you can perform completed move entries collecting and exclude them out from the initial request before the retry. 😉 Not very convenient, but it's something.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
