Index was broken, SearchV2 lost answer

[S. Yasuo]

Hi,

I'd like to understand Indexing for Folders.

My service suddenly stopped answering SearchV2, which returned no match files.

This folder had over 170,000 files.

I recovered following steps,

1. Rename old folder
2. Create new folder as same name
3. Move included files from old to new, take care count of files.

After 1.5 days, my service has recovered.

I have questions for same trouble shooting.

A. What's the reason Index Broken?  Count of files?  I'd like to know the red line numbers of files.

B. What is the best way for Index Recovering?  Can I reorganize Index manually some API call?

C. Anything else way for this trouble shooting?  1.5 days is not so short.

Regards,

Y. Shimizu

[Greg-DB]

A. Due to indexing and caching, sometimes Dropbox search results may not be immediately updated and available, especially when there are many files/folders like this. I don't have a specific number of files/folders to offer as guidance for when this may occur though.

B. The Dropbox search system will automatically update its indexes/caches, though this can take some time. There isn't a way to force this manually via an API call though.

C. There isn't really any way to troubleshoot this externally, as this occurs on the Dropbox backend. Especially for very large amounts of files/folders though, you may instead want to use the ListFolder/ListFolderContinue functionality for listing the entries, which you can then filter client-side.

[S. Yasuo]

Many thanks  @Greg-DB,

Mmmm, it's not expected but understood answer.

I try to find safety numbers of files.

I didn't think 170,000 was not so many, but it occurred.

I have to change my service specification.

Thanks again!