cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Want to learn some quick and useful tips to make your day easier? Check out how Calvin uses Replay to get feedback from other teams at Dropbox here.

Dropbox API Support & Feedback

Find help with the Dropbox API from other developers.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Re: cannot copy files with filesCopyBatchV2

cannot copy files with filesCopyBatchV2

tiamat
Helpful | Level 6
Go to solution

I am trying to copy some files from my `Camera Uploads` folder to another folder `Videos`

 

first I do

 
const { async_job_id } = await dropbox.filesCopyBatchV2({
      entries,
      autorename: false,
    });    

This seems to work because I get back a long string for async_job_id

Then I do the following:

while (true) {
    try {
      let response = await dropbox.filesCopyBatchCheckV2({ async_job_id });
      if (response['.tag'] != 'in_progress') {
        break;
      }
      await sleep(5000);
    } catch (error) {
      break;
    }

What happens is that I hit filesCopyBatchCheckV2 endpoint 5 or 6 times; I get back a response of in_progress each time; then I get a response with a status of 409, statusText of "Conflict" and an error_summary of internal_error.

 

No files get transferred.

 

Please help!

 

1 Accepted Solution

Accepted Solutions

Здравко
Legendary | Level 20
Go to solution

@tiamat wrote:

...

const { async_job_id } = await dropbox.filesCopyBatchV2({
      entries,
      autorename: false,
    });    

... I get a response with a status of 409, statusText of "Conflict" and an error_summary of internal_error.

...


Hi @tiamat,

Seems, someone (one or more) file with same name reside at destination already. 😉 If you are forbidding autorename, it's coming up as an error.

Hope this helps.

View solution in original post

2 Replies 2

Здравко
Legendary | Level 20
Go to solution

@tiamat wrote:

...

const { async_job_id } = await dropbox.filesCopyBatchV2({
      entries,
      autorename: false,
    });    

... I get a response with a status of 409, statusText of "Conflict" and an error_summary of internal_error.

...


Hi @tiamat,

Seems, someone (one or more) file with same name reside at destination already. 😉 If you are forbidding autorename, it's coming up as an error.

Hope this helps.

Greg-DB
Dropbox Staff
Go to solution

@tiamat I see you already got some help here, but it's worth noting that there can be other causes of failures like this, so if you still need help tracking down what's wrong, feel free to contact us directly with the job ID.

Need more support?