I am using HTTP API to obtain the story executed so far during a conversation. Story API documentation . http://localhost:5005/conversations/{conversation_id}/story When database details are present in endpoints.yml to save conversations in tracker store, fragments of the story obtained from the above API are appended at the top of the response markdown text. When database details are not present, fragments of the story obtained from this API are appended at the bottom of the response markdown text. I am parsing the response markdown text obtained from this API to check if a form is completed or not. So the order of fragments in the story matters to me. I feel the order of fragments obtained should remain the same. Please let me know if I am missing something.

@btotharye Can you please look into this issue?

I can try to reproduce this, if you have any logs our output showing this that would also be helpful and for your config part in the endpoints.yml is it just a normal tracker store setup and what db are you using? Thanks

Problem in retrieving an end-to-end story in HTTP API

Rasa Open Source

tonysinghmss (Manishankar Singh) November 7, 2019, 3:34pm 4

I am using a normal tracker store using postgresql. Somehow this issue got resolved. If I face it again, I will let you know.

Thanks.

Topic		Replies	Views
Retrieve end-to-end story via HTTP API when using an external tracker store Rasa Open Source	1	168	February 17, 2023
Story is in inverted order when requesting it through HTTP api Rasa Open Source	1	677	June 19, 2019
Stories are not working at all Rasa Open Source	6	2051	September 2, 2020
How to store conversations in stories.md file Rasa Open Source	6	1917	September 27, 2019
The story is different in rasaX and api Rasa Open Source	1	372	April 15, 2021

Problem in retrieving an end-to-end story in HTTP API

Related topics