nedyr Actually I meant “re-index” command, as re-scan typically would not have any effect, as it is looking for changes, while re-index just purges all known data about the file from db and indexes it as new.
However, since rescan in your case had effect, that actually narrows down the search area for us. As I understand, what is happening is Tonfotos writes updated file to the disk, and saves to the database it’s modification time, to avoid indexing it next time until someone modifies it. And, as I understand, program finishes that without any errors.
However, when you do re-scan, program finds out, that modification date is ALREADY DIFFERENT from what it had been right after Tonfotos has updated it. That is why it indexes it again. It looks like someone had automatically reverted file to its previous version right after it was modified by Tonfotos.
Do you have any idea why this is happening? Where exactly those files are stored? Is this regular internal drive or some sort of virtual folder in the Cloud? Is there any antivirus protection running in the background that tries to interfere with file modification?
