Renaming files server-side to solve duplicate issues results in wrong local files count

Existing users have a lot of duplicate files. So trying to rename the duplicates in server side (to give unique names) and see if the duplicates are gone was not successful.
After server side rename, Nuxeo Drive created some more duplicates. This does not happen for all files, but for some files if there are hundreds of rename operations in server side.
For example:

1. There are 7 files with the name "BUG.jpg" in the same folder in server side.
2. drive tries to sync these files and syncs one file.
3. The remaining files are not synced because duplicate names like bug (1).jpg is disabled. So drive shows 6 errors.
4. rename all the files in server side using NuxeoDrive.Rename operation.
   example:
   "BUG-139f6f81-ec85-43c6-9975-609d3ce7c81c (RenamedBySystem).JPG"
   "BUG-db7c7e76-fbec-4f0b-9b5e-b5e11982b9cc (RenamedBySystem).JPG"
   "BUG-70db741b-9482-4b06-b17e-884e88741bf1 (RenamedBySystem).JPG"
   "BUG-1475321a-d935-49b2-81da-5d5182c9a7a3 (RenamedBySystem).JPG"
   "BUG-e9d9ef05-a31b-4c42-8460-50631046a270 (RenamedBySystem).JPG"
   "BUG-7793460f-e00e-4004-b5d5-a62efb8090e8 (RenamedBySystem).JPG"
   "BUG-c6b61e24-c0f9-4f91-886f-b1ca10eb378e (RenamedBySystem).JPG"
5. Wait for drive to sync the changes.
6. Drive successfully syncs the changes, but creates one more file with the name BUG.jpg in the same folder.