rasa: Preset Slots are missing in tracker

Rasa version: 1.10.0

Rasa X version (if used & relevant): 0.29.1

Python version: 2.7.17

Operating system (windows, osx, …): linux, docker

Issue:

Slots that are defined in domain.yml with an initial_value are not included within the tracker information that can be received using the HTTP API (https://api/conversations/{conversation_id}/tracker)

Error (including full traceback):

Command or request that led to error:

https://api/conversations/{conversation_id}/tracker

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

location:
    type: unfeaturized
    initial_value: Hamburg

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 22 (11 by maintainers)

Most upvoted comments

@leondroidgeeks thanks a lot for your input. the slots values in the tracker are inconsistent between the two APIs, and we’ll look into fixing that. In the meantime, would querying /core/ directly be an option for you?

So the GET /core endpoint using the RASA_TOKEN calls the Rasa Open Source APIs?

yes that’s right, it queries Rasa Open Source directly

Is there any other difference between these two APIs for getting the tracker?

There could be a few other differences - we’ll look into getting the two tracker endpoints aligned as much as possible

ricwo on Jun 23, 2020

Mmmh then I will have a second look at this because as I remember, I couldn’t find my preset slot under the slots key in the response I get from the /tracker endpoint. (I am interested in the slots key, not the events) Currently I have some troubles with my Rasa Server (I just posted in the forum about this), but I will get to it when I can talk to bot again!

leondroidgeeks on Jun 17, 2020