Hi @roscoe,
Apologies for the inconvenience here.
It is actually Microsoft that creates those tmp files. They occur when OneDrive for Business accepts the upload, creates the tmp file for that upload, and then hits an error when trying to finish/commit that file.They are supposed to clean them up within 24 hours…
Their upload behavior has some flaws that perpetuate this type of occurrence. odrive can’t actually see those files at all, since they aren’t returned in the API calls. So, an error is generated initially on the OD4B side; odrive’s upload request is returned as an error; odrive marks the file for upload reattempt. The subsequent upload attempt can then fail because the tmp file exists (Microsoft returns: “An unspecified error has occurred”, which is pretty much useless to take any action on). Then it is just a vicious cycle of the same thing, at that point.
Unfortunately, I am not really sure how it can be addressed without Microsoft adjusting their upload flow behavior. I had missed a response from them last month in the bug report, so I am following-up again, to see what their recommendation is, if they cannot fix on their side.