Rasa: Tried to set non existent slot 'count_list'. Make sure you added all your slots to your domain file.

Created on 17 Jun 2019  ·  15Comments  ·  Source: RasaHQ/rasa

Rasa version: 1.1.3

Rasa X version (if used & relevant):Not using

Python version: 3.6.8

Operating system (windows, osx, ...): Windows 10

Issue: When i tried to use interactive learning getting this error though i mentioned all the slots in domain file.. It was working well earlier in rasa==1.0.7 version.

Error (including full traceback):

2019-06-17 19:35:24 DEBUG    rasa.core.tracker_store  - Recreating tracker for id 'ca2c5d2b07f140bb90668586f1c28b10'
2019-06-17 19:35:24 DEBUG    rasa.core.processor  - Received user message 'list all impacted cis' with intent '{'name': 'ci_info', 'confidence': 0.9596539735794067}' and entities '[{'start': 0, 'end': 4, 'value': 'List', 'entity': 'count_list', 'confidence': 0.9737233844587407, 'extractor': 'CRFEntityExtractor', 'processors': ['EntitySynonymMapper']}, {'start': 9, 'end': 17, 'value': 'Impacted', 'entity': 'impa_noimpa', 'confidence': 0.9975736855043231, 'extractor': 'CRFEntityExtractor', 'processors': ['EntitySynonymMapper']}]'
2019-06-17 19:35:24 DEBUG    rasa.core.processor  - Current slot values:
        count_list: List
        filter1: None
        impa_noimpa: Impacted
        item_text: None
        item_value: None
        open_close: None
2019-06-17 19:35:24 DEBUG    rasa.core.processor  - Logged UserUtterance - tracker now has 4 events
2019-06-17 19:35:25 DEBUG    rasa.core.tracker_store  - Recreating tracker for id 'ca2c5d2b07f140bb90668586f1c28b10'
? Is the intent 'ci_info' correct for '[list](count_list:List) all [impacted](impa_noimpa:Impacted) cis' and are all entities labeled correctly?  Yes
2019-06-17 19:35:30 DEBUG    rasa.core.tracker_store  - Recreating tracker for id 'ca2c5d2b07f140bb90668586f1c28b10'
2019-06-17 19:35:30 DEBUG    rasa.core.policies.memoization  - Current tracker state [None, None, None, {}, {'entity_count_list': 1.0, 'intent_ci_info': 1.0, 'slot_count_list_0': 1.0, 'slot_impa_noimpa_0': 1.0, 'prev_action_listen': 1.0, 'entity_impa_noimpa': 1.0}]
2019-06-17 19:35:30 DEBUG    rasa.core.policies.memoization  - There is a memorised next action '8'
2019-06-17 19:35:30 DEBUG    rasa.core.policies.ensemble  - Predicted next action using policy_0_MemoizationPolicy
2019-06-17 19:35:30 DEBUG    rasa.core.tracker_store  - Recreating tracker for id 'ca2c5d2b07f140bb90668586f1c28b10'
2019-06-17 19:35:30 ERROR    rasa.core.trackers  - Tried to set non existent slot 'count_list'. Make sure you added all your slots to your domain file.
2019-06-17 19:35:30 ERROR    rasa.core.trackers  - Tried to set non existent slot 'impa_noimpa'. Make sure you added all your slots to your domain file.
------
Chat History

 #    Bot                                                                                        You
────────────────────────────────────────────────────────────────────────────────────────────────────────────
 1    action_listen
────────────────────────────────────────────────────────────────────────────────────────────────────────────
 2                                         [list](count_list:List) all [impacted](impa_noimpa:Impacted) cis
                                                                                       intent: ci_info 0.96
────────────────────────────────────────────────────────────────────────────────────────────────────────────
 3    slot{"count_list": "List"}
      slot{"impa_noimpa": "Impacted"}

Command or request that led to error:

rasa interactive --debug --endpoints endpoints.yml

Content of configuration file (config.yml) (if relevant):



Content of domain file (domain.yml) (if relevant):


type

All 15 comments

Please post your domain file as well

@akelad Please find the domain file

"""
slots:
item_value:
type: text
item_text:
type: text
open_close:
type: text
count_list:
type: text
impa_noimpa:
type: text
filter1:
type: text

intents:

  • greet
  • farewell
  • how_doing
  • out_of_scope
  • thank
  • item_info
  • count_list_info
  • ci_info
  • ticket_ci
  • development

entities:

  • open_close
  • item_value
  • item_text
  • count_list
  • impa_noimpa
  • filter1

templates:
utter_greet:
- text: "Hello! I'm customerbot🤖 and will be happy to help you with Ticket and CI information"
- text: "Hi! I'm customerbot🤖 and will be happy to help you with Ticket and CI information"
- text: "Greetings for the day, I'm customerbot🤖 and will be happy to help you with Ticket and CI information"

utter_farewell:
- text: "Goodbye! 👋"
- text: "Bye-Bye! 👋"
- text: "Bye 👋, was nice talking to you!"

utter_how_doing:
- text: "I'm very well, thank you."
- text: "I'm good, thanks!"
- text: "I'm great! Thanks for asking."

utter_anything_else:
- text: "Is there anything else I can help you with?"

actions:

  • utter_greet
  • utter_farewell
  • utter_anything_else
  • utter_out_of_scope
  • utter_how_doing
  • action_item_info
  • action_count_list_info
  • action_ci_info
  • action_ticket_ci
    """

I got this error too, but it seems to work fine anyway

@GianMariaPandolfi yeah it works.. Thank you...

I also got this issue, that is driving my and my employer crazy

Ok this is strange, just to clarify so we can try and reproduce this, you're running the command rasa interactive right? with a newly trained model?

Ok this is strange, just to clarify so we can try and reproduce this, you're running the command rasa interactive right? with a newly trained model?

Yes @akelad

alright, @imLew would be great if you could try and reproduce this

Same issue. initially happened with Rasa 1.1.1
I upgraded to Rasa 1.1.3, retrained my models, but the issue still persists.
I'm not noticing any issues with performance, everything still seems to be working as expected, just getting the errors
Screen Shot 2019-06-20 at 6 07 18 PM

Domain file:

entities:
- conf_room_name
- building_name
- food_type
- duration
- occasion
- menu_type
- station_name
- country
- colleague_name
- cafe_name
- query_location
- restrictions
- start_time
- time_period
- query_date
slots:
  building_name:
    type: unfeaturized
  cafe_name:
    type: unfeaturized
  colleague_name:
    type: list
  conf_room_name:
    type: text
  country:
    type: unfeaturized
  domain:
    type: unfeaturized
  duration:
    type: unfeaturized
  food_type:
    type: unfeaturized
  menu_type:
    type: unfeaturized
  occasion:
    type: text
  occasion_count:
    type: unfeaturized
  occasion_dates:
    type: unfeaturized
  occasion_titles:
    type: unfeaturized
  query_date:
    type: text
  query_location:
    type: text
  query_person_name:
    type: text
  requested_slot:
    type: unfeaturized
  restrictions:
    type: unfeaturized
  room_available:
    type: bool
  rooms_available:
    type: bool
  start_time:
    type: text
  station_name:
    type: unfeaturized
  time_period:
    type: text

@akelad Yes, this happens even on the latest master, I will see if I can figure out why

Hi i have the same issue i renamed a slot and did it every where.
also search the whole project folder nowhere a trace find of the slot name and i get this now every time
Screen Shot 2019-07-06 at 01 32 12

@dptelecom the PR addressing the problem should be merged today, please try again using the master branch once this issue is closed.

I had this same issue yesterday. in interactive mode i was getting an error while trying to set entities and slot(my domain file had entities and slots correctly defined):
error: rasa.core.trackers - Tried to set non existent slot. Make sure you add all slots to your domain.

At first i thought i needed trackers.py update but when i looked into nlu.md data that interactive mode generated i found some inconsistencies in entity extraction(there were new entities and intents i didnt want). I fixed those inconsistencies and i no longer get this error.

What i believe:
While training rasa in interactive mode, we correct the entities and intents. During export, interactive adds the wrong classified intents and entity extraction to the nlu.md file. When i removed them tracker worked fine for me.

@TayyibahR Please create a seperate issue for this, as it sounds like the underlying problem is different. Or, if you could turn your fix into a PR that would be even better :D!

Same issue. Any fix?
Edit: Had same issue. Fixed it by fixing indentation of domain yml file.

Was this page helpful?
0 / 5 - 0 ratings