An indexed folder keeps re-appearing in a Database

An indexed folder keeps re-appearing at the root level of one of my databases after I move it to the trash. Is this because it is somehow registered in the sync file, so the sync file puts it back again? If so how to I force it to recognise that I do not want an indexed folder there any more?

I guess I could set up a replacement database and move everything over one by one except for the indexed folder, and set up new sync etc. for that database, but it’s a large one, I’d rather not go that route if there’s a better fix available.

FWIW it’s an iCloud drive root level folder (Documents) that is indexed. Which may or may not have been a terrible idea, but anyway I want to remove it from the database so there it is.

I want it removed mainly because I don’t need it there any more, but moreover I’m finding it messes up sync to DTTG on my iOS devices, such that that database doesn’t sync at all to iOS when the indexed folder is there.

Did you empty the trash?

I was careful to empty it only emptying what was in database; I assumed that if I selected files or files and folders, it would remove the Documents folder from iCloud itself, although I guess I might be wrong about that or could try a failsafe approach to doing so? Someone correct me if I need to select ‘Files and Folders’ when emptying.

No, you would not choose Files and Folders in this case. You would choose Only in Database to remove the reference from the database.

What sync method are you using?

1 Like

Thank you. I am syncing via WebDAV to NAS (not local) which is far and away my preferred option to any of the others…

You didn’t index your entire home directory, did you?

No, only the Documents folder (which is still pretty large)