Suggesters ignore the "Contains all of these words" setting in the underlying view

Thanks for reporting this problem, and sorry it took me so long to get back to you!
The behavior of the autocompletion depends on several factors – e.g., the selected suggester plugin(s) and the search backend you’re using.
In principle, though, we do use the view’s own settings to create the underlying search query. However, what then happens with this information depends on the afore-mentioned factors.

In general, autocomplete is not an exact science, there will unfortunately almost always be situations where the results are not as expected/desired, and most of the implementations available are also rather simple, not designed to be as accurate as possible but just easy to use and maintain. If you require more reliable results, or have other specific requirements, you’re probably better off writing your own suggester plugin (or hiring someone to do that).

With that said, if you would still like a more specific reply from me, you’ll need to tell me more about your setup, how you configured both the search and the autocomplete.

I am getting the same thing with Search API Solr. Autocomplete creates suggestions for what it thinks you are typing, but then the next words you receive as suggestions create phrases that will never return results, unless you use 'contains any'. It's somewhat of weird UX to me. I would expect autocomplete to complete phrases of what I am typing instead of any hit on what I am typing in.