I am here to express concern with poor performance using the move_batch API endpoint. After investing significant resources into restructuring my application to queue up and check on these types of asynchronous requests as suggested in response to problems I was having attempting to move files synchronously, I frequently encounter move_batch requests failing for no identifiable reason.
I'm particularly frustrated at the moment by one particular "job" that fails no matter how many times I repeat it (dbjid:AADtrwnsGSbXhQlQpXlcArmBS9glb986C5DsdcMN4rA2MixOJK7nnJ3WAj0QNIXF8q_Ry2vBb2y7t0Zabz-nieBF). It's a few hundred files, nothing too crazy, but I've been reattempting it over and over for the past two days and it fails each time after about 10 minutes. Other similar jobs go through fine. It doesn't make any sense to me.
It would be really helpful to get a clear answer on why this is so slow and unreliable.
Thanks for the feedback! It sounds like this is a followup to your earlier thread this year about this. I'm afraid I don't have any news or changes to report on this though. I know this performance still isn't very good, so I'll bring this up with the team again.
Regarding that particular job that is consistently failing, can you share the full request and response? (Just be sure to redact the access token of course.) That should help me investigate it in particular. Please open an API ticket if you'd prefer to share privately.
We love to learn from the educators who use Dropbox. Whether you teach kids, teens, adults or a combination of all three, we want to know what apps and integrations you use with Dropbox to help with teaching. Which of the ones below is your favorite, or most used tool?