Hi @deanneese,
Apologies for the confusion here. This is a situation we are aware of and are working on optimizing.
Bulk operations, such as syncing all files in a folder, can hit service exceptions during their run. The larger the operation (number of files/folders) the more likely an exception will be hit along the way. Some services are more prone to exceptions than others; things like rate limiting, network timeouts, etc… Some of these exceptions can halt the bulk operation, with the end result being that a subset of files has not been synced. Issuing the same command again will pick up the remaining items, but it is possible to hit another exception that halts the op.
We realize this is not optimal behavior and that all efforts should be made to complete the user’s intended result. If your goal is to migrate from one storage to another then this can be a problem, as you have stated above.
The easiest way to determine if an entire structure has been synced is to search for any instances of a .cloud/.cloudf file in the structure. There are also some simple scripts that can be run to essentially “loop until done” on a structure. I have posted one or two in the forum for folks as a more automated way to ensure that a structure is 100% downloaded, hitting any of the potential stragglers. Its a little bit primitive, but it has worked for their use cases. Here is an example: