How can a recursive download be forced to continue, despite the storage exceptions that odrive may encounter, so that I can sync everything I want to download?

For large bulk downloads, if odrive encounters numerous exceptions, rate limits, or certain types of “critical” errors, it will abort the action instead of just blindly retrying to infinity. This can be frustrating if a user wants to download lots and lots of content, but the storage service is returning frequent errors. For scenarios like these, it is possible to use the CLI to essentially perform a brute-force “download until done” action. It is not elegant, but it can be useful for some folks. One of the reasons that odrive stops syncing in these cases is because some integrations can “react” to what they consider aggressive behavior (continually trying to download files that they cannot or will not provide at that time, continuing to make requests when they are having service issues, continuing to make requests when an API throttle has been imposed, etc…) and can then do things like block or severely throttle your account. Keep this in mind if you wish to proceed with this method…

How can I force a recursive sync (download) with the CLI?

I Have a Question

Tony March 11, 2020, 11:21pm 4

Hi @allen,
This post goes through the command in more detail and through several iterations. It should provide the details you are looking for:

Running parallel processes will allow multiple concurrent downloads.