I took a look at the diagnostics and here’s what I see:
Since these files are larger, you look to be hitting a known issue with Amazon and large file uploads. (Here is a post about it: Amazon Drive Sync to 98% - Repeat)
Often Amazon will return errors when uploading a large file, indicating that the upload has failed and we should try again. In some of these cases the file actually does make it to Amazon and they fully process it (after a period of time). Now odrive, unaware that the file actually made it up, retries the upload. At this point a “new” version of this file has appeared that was not there before (the file that was reported as having failed but actually made it up). odrive sees this new version, thinks that there must have been an edit of the this file elsewhere, and decide that it needs to create a conflict file to prevent any data loss. The conflict is created and uploaded.
I realize the above is a bit verbose. The short of it is:
Amazon throws an error on upload, but it actually succeeds. odrive retries the upload but finds a new version of the file now exists. odrive creates a conflict file, unaware that the new version is actually the version it previously tried to upload.
We are working on ways to try to get around this quirky Amazon behavior. In the meantime there isn’t a solid workaround for this, but a few ideas:
- Delete the conflict file, as it is most likely the same as the non-conflict file (double-check it though).
- If you are making edits to large files, save them as new file names (ABC_v2.psd, for example). The conflict scenario happens on file updates, vs new file uploads. On new file uploads, odrive is able to better deal with the sudden appearance of a new file and can usually resolve it out.