>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3570274. --> Reported by: [scott_euser](https://www.drupal.org/user/3267594) Related to !18 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>When analysing user intent (e.g. in an earlier search api process plugin), if the intent is e.g. an exact match/not a question/a name, the best result may be better achieved via Solr/Database/other, and not AI Search. It should be possible therefore for process plugins to tell the boost plugins not to run.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>N/A</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Add a 'skip_ai_search' option check on the query.</p> <h3 id="instructions">How to test</h3> <ol> <li>Create any search api plugin on your main index (e.g. database or solr) and ensure it runs before the boost</li> <li>Use<br> <div class="codeblock"> <pre><span style="color: #000000"><span style="color: #0000BB">&lt;?php<br>&nbsp;$query</span><span style="color: #007700">-&gt;</span><span style="color: #0000BB">setOption</span><span style="color: #007700">(</span><span style="color: #DD0000">'skip_ai_search'</span><span style="color: #007700">, </span><span style="color: #0000BB">TRUE</span><span style="color: #007700">); <br></span><span style="color: #0000BB">?&gt;</span></span></pre></div> </li> </ol> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ol> <li>MR</li> <li>Backport to 1.3/1.2</li> </ol> <h3 id="summary-ui-changes">User interface changes</h3> <p>N/A</p> <h3 id="summary-api-changes">API changes</h3> <p>N/A</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>N/a</p>