So, currently, our workaround for large files is to upload them via the browser, not file explorer. But, unfortunately, we needed the workflow more than we needed the convenience of easy uploads. A workflow was trying to modify the large file while it was being downloaded through everyone’s sync client so it encountered a sort-of “save conflict” while syncing both ways. We eventually used workflow to help us delete any files created or changed with ComputerName-ComputerName-ComputerName in the title because if you’re not fast enough, the process will just continue its copy, download, upload cycle.Īs for workflows, we noticed if we turned off workflows on the document library in question, we didn’t get the same issue. It becomes a bit of a game to try to actually delete the files, but I would suggest trying to delete the file from the browser, and not file explorer so you catch it upon creation and not after download. And many of the files you’re left with will oddly be corrupt 0 KB files. Due to that size, and multiple people syncing the same library, I imagine it’s pinging back and forth as it downloads, copies, uploads, discovers a conflict, downloads, copies, etc. We’ve only run into this issue when the file in a frenzy is significant in size. I don’t know that there is one solution to this problem, either, so I’m going to share a number of them we’ve used and hope that one (or all) of them will help you.īasically a file is added through file explorer (a cloud library in OneDrive or SharePoint being synced locally to your computer) but then after a moment a notification appears which says “You now have two copies of a file we couldn’t merge the changes in ” and then the filename is appended with your computer name again and again until eventually the filename is too long and is harder to delete.
If you’ve seen a similar notification, I empathize with your pain.
0 kommentar(er)
