A big part of the problem is that you are using relevance to check all files on a system. This is in general a bad idea. It is very slow and will have negative consequences to the Client Eval Loop, among other issues. It will also tend to time out over and over and never actually work.
This sort of search is much better done with a task that is run either once, or on an interval with the results saved to a file, and then those results can be checked with an analysis property.
Here is an example of an appropriate use of the descendants relevance because it is limited to a single folder on the system, not all files and folder of the system: Relevance based on folder size
See also: Locate and replace a file under User Data (still not ideal)
See related posts:
- 2 parts: Find Files vs Dir /s /a ; How to store "find files" results in a file
- File search return error
- Parsing file.txt and if exist one of value in folder
- Trying to exclude a directory from descendants search
- Relevance issues
- IllegalFileName check (or Continuing on Error)
- Regex to find files with social security numbers