I’m not sure. I had mine set to “0” for a few scans. In my small environment, I run the Initiate Software Scan as a daily policy action.
What you might consider doing is running this relevance on one of the problematic machines:
concatenation "%0a" of (image paths of instances of application usage summaries)
This should confirm that the error situation exists on that machine.
Next, update the setting to “0”, and run the relevance.
Finally, back to “1”, and run the relevance.
That could tell you if you need to wait for a scan.