# Problem with response selector / retrieval intent

**URL:** <https://forum.rasa.com/t/problem-with-response-selector-retrieval-intent/38679>\
**Category:** Rasa Open Source\
**Created:** [January 5, 2021, 10:04pm UTC](https://forum.rasa.com/t/problem-with-response-selector-retrieval-intent/38679 "2021-01-05T22:04:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![wvalverde67](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/wvalverde67/32/12293_2.png) [@wvalverde67](https://forum.rasa.com/u/wvalverde67)\
**Post date:** [January 5, 2021, 10:04pm UTC](https://forum.rasa.com/t/problem-with-response-selector-retrieval-intent/38679/1 "2021-01-05T22:04:37Z")

</div>

Trying to configure my bot with a simple set of general responses.

- In my config.yml I have the “response selector” option in my pipeline with “retrieval intent”: chitchat

- nlu and domain files have the corresponding intents/responses

When I used RASA X in the monitor windows I get the following message:

 ![Captura.PNG](https://europe1.discourse-cdn.com/flex013/uploads/rasa/original/2X/1/177cb194a6b763f4e855e1cf17d1d10084b85037.jpeg)

And when I used RASA SHELL it’s a similar message:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/rasa/original/2X/1/137d0f0ec423be6811f04b910b4837da20c63cfd.png)

Seems to be something related to ACTION SERVER.

Thanks in advance

---

<div class="post-metadata">

**Author:** ![m-vdb](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/m-vdb/32/10526_2.png) [@m-vdb](https://forum.rasa.com/u/m-vdb)\
**Post date:** [January 6, 2021, 3:17pm UTC](https://forum.rasa.com/t/problem-with-response-selector-retrieval-intent/38679/2 "2021-01-06T15:17:55Z")

</div>

Hello @wvalverde67, thanks for your question!

Would you mind sharing your `config.yml`, `domain.yml` files as well as the file containing the responses (likely to be the `nlu.yml` file). That way I can better assist you.

💡 worth noting that we have a [step by step guide on how to setup response selectors](https://rasa.com/docs/rasa/chitchat-faqs#step-by-step-guide-on-using-response-selector-for-faqs-and-chitchat) and you can also fin examples in [our repository here](https://github.com/RasaHQ/rasa/tree/master/examples/responseselectorbot). These links might help you debug your setup.

---

<div class="post-metadata">

**Author:** ![wvalverde67](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/wvalverde67/32/12293_2.png) [@wvalverde67](https://forum.rasa.com/u/wvalverde67)\
**Post date:** [January 6, 2021, 3:32pm UTC](https://forum.rasa.com/t/problem-with-response-selector-retrieval-intent/38679/3 "2021-01-06T15:32:11Z")

</div>

I really appreciate your help.

config.yml [config.yml](https://forum.rasa.com/uploads/short-url/owEb8xWqLagp8J8t0H0BCDa2HxX.yml) (949 Bytes)

domain.yml [domain.yml](https://forum.rasa.com/uploads/short-url/1QHFwDPab3j5ufFqtqRZ7Kbk8m9.yml) (3.0 KB)

nlu.yml [nlu.yml](https://forum.rasa.com/uploads/short-url/kKA91YsgYJcJ8Sb1qBRwdCKk9Z.yml) (8.7 KB)

Thanks!!!

---

<div class="post-metadata">

**Author:** ![wvalverde67](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/wvalverde67/32/12293_2.png) [@wvalverde67](https://forum.rasa.com/u/wvalverde67)\
**Post date:** [January 8, 2021, 10:21pm UTC](https://forum.rasa.com/t/problem-with-response-selector-retrieval-intent/38679/4 "2021-01-08T22:21:52Z")

</div>

hello @m-vdb

Do you have news?

Thanks in advance!!!

---

<div class="post-metadata">

**Author:** ![m-vdb](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/m-vdb/32/10526_2.png) [@m-vdb](https://forum.rasa.com/u/m-vdb)\
**Post date:** [January 12, 2021, 5:43pm UTC](https://forum.rasa.com/t/problem-with-response-selector-retrieval-intent/38679/5 "2021-01-12T17:43:34Z")

</div>

Thanks for sharing @wvalverde67 and sorry for the later reply. Your training data and config seem correct. There is maybe one thing that is incorrect but I’m not sure it’s leading up to this error: your `config.yml` file contains a ResponseSelector component with `retrieval_intent: faq` but you do have have the `faq` intent configured elsewhere.

Going back to the screenshot you shared, the first one looks like a compatibility issue between Rasa and Rasa X. Would you mind sharing the versions you’re using?

---

<div class="post-metadata">

**Author:** ![wvalverde67](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/wvalverde67/32/12293_2.png) [@wvalverde67](https://forum.rasa.com/u/wvalverde67)\
**Post date:** [January 12, 2021, 6:09pm UTC](https://forum.rasa.com/t/problem-with-response-selector-retrieval-intent/38679/6 "2021-01-12T18:09:05Z")

</div>

Hello @m-vdb

I’m trying to get help posting differents times and subjects but unfortunately … I have no response. Here is a link:

[http://forum.rasa.com/t/retrieval-intent-chitchat/38426](http://forum.rasa.com/t/retrieval-intent-chitchat/38426)

I think the RASA stack is awesome, but some details about documentation … even support of the community need more attention.

Tx

---

<div class="post-metadata">

**Author:** ![m-vdb](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/m-vdb/32/10526_2.png) [@m-vdb](https://forum.rasa.com/u/m-vdb)\
**Post date:** [January 19, 2021, 5:29pm UTC](https://forum.rasa.com/t/problem-with-response-selector-retrieval-intent/38679/7 "2021-01-19T17:29:19Z")

</div>

@wvalverde67 it sounds like @Juste was able to solve your issue [here](http://forum.rasa.com/t/retrieval-intent-chitchat/38426/7) by founding out about a typo (Thanks Juste!). It looks that I need to change my glasses 👀 👓

Can we consider this issue resolved?

---

<div class="post-metadata">

**Author:** ![wvalverde67](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/wvalverde67/32/12293_2.png) [@wvalverde67](https://forum.rasa.com/u/wvalverde67)\
**Post date:** [January 19, 2021, 6:29pm UTC](https://forum.rasa.com/t/problem-with-response-selector-retrieval-intent/38679/8 "2021-01-19T18:29:02Z")

</div>

Hello @m-vdb

Yes, she helped me!!! I think besides the misspelling was a problem in my pipeline.

Thank you both!!!
