Can the tracker recover conversations after a server restart?

digitalWestie · January 16, 2021, 1:15pm

I have a custom tracker store that persists conversations to CouchDB. The code can be found here: A Rasa tracker implementation for couchDB · GitHub

I can see conversations being stored in the database, and I can see from logs things working ok. I have a web-frontend based on chatroom repo (GitHub - digitalWestie/chatroom: React-based Chatroom Component for Rasa Stack) that I’m using as my frontend. When I refresh the page it fetches the tracker from the API endpoint and I can continue conversation.

So far so good. However, if I refresh the page after restarting the rasa server then it seems to restart the conversation from scratch. I can see from the database the tracker has been completely reset from the beginning.

My guess is this behaviour is down to way the lock store works. What I’d like to happen is for my conversations to be picked up by the server after it has been restarted. I can understand this might make sense if I had lots of instances running for load balancing purposes, but in my case I’d just like to run the one server. Can anyone advise?

digitalWestie · January 17, 2021, 9:26pm

Update- I tried using the Redis lock store instead of the memory lock store. No change in behaviour…

digitalWestie · January 21, 2021, 4:23pm

I see that it’s possible for sessions to expire as a result of my Session configuration# - in my case I have session_expiration_time set to 0 so that sessions do not expire.

digitalWestie · January 21, 2021, 4:58pm

Looking through the code, the two conditions that dictate a new session are whether the tracker has any events, or whether the session has expired -

github.com

RasaHQ/rasa/blob/954e4734d479924df7211cd3bc5503285d54a66b/rasa/core/processor.py#L182


An 'action_session_start' is run if the latest tracker session has expired,
or if the tracker does not yet contain any events (only those after the last
restart are considered).
Args:
    metadata: Data sent from client associated with the incoming user message.
    tracker: Tracker to inspect.
    output_channel: Output channel for potential utterances in a custom
        `ActionSessionStart`.
"""
if not tracker.applied_events() or self._has_session_expired(tracker):
    logger.debug(
        f"Starting a new session for conversation ID '{tracker.sender_id}'."
    )
    await self._run_action(
        action=self._get_action(ACTION_SESSION_START_NAME),
        tracker=tracker,
        output_channel=output_channel,
        nlg=self.nlg,
        metadata=metadata,

It seems like either my configuration isn’t being read properly, or the tracker isn’t loading, or loading before this condition.

digitalWestie · January 21, 2021, 9:34pm

ok, it turns out it was my fault all along. Selecting a document using the Couch DB client isn’t behaving as I’d expected! I’ve updated my gist for anyone wanting to use the Couch DB tracker!

gist.github.com

https://gist.github.com/digitalWestie/f1f01461dec7abb42e1ca852567d13c6

README.md

This is a CouchDB implementation for a Rasa (2.0) tracker that makes use of the Cloudant CouchDB API wrapper.

To use, you'll need to install the cloudant package with pip, or add to your requirements.txt (`cloudant==2.14.0`)

Copy `tracker.py` into `project-root/couch_tracker/` directory. Next, configure your endpoint details based on the example, and insert into your endpoints yml.

That should be it! Let me know if it works, or doesn't- @digitalWestie x


**Licence**

This file has been truncated. show original

endpoints.yml

#Example settings to be inserted into endpoints.yml
tracker_store:
  type: couch_tracker.tracker.CouchTrackerStore
  url: 172.20.128.2
  port: 5984
  username: mycouchuser
  password: mycouchpass
  db: mydbname

#...

tracker.py

import json
import logging
from typing import (
    Any,
    Callable,
    Dict,
    Iterable,
    Iterator,
    List,
    Optional,

This file has been truncated. show original

uddaishya22 · September 22, 2022, 8:44am

Hi @digitalWestie ! I am using InMemory Tracker store. and after server restart I want to recover few last events from sqlite tracker store (that i am using to store tracker state). How can I do that, earlier I tried to cinfigure ‘action_session_start’ default action but that works only when conversation session expires. will you pl help me in achieving my use-case?

digitalWestie · October 6, 2022, 11:24am

You’ll need to configure endpoints.yml file to use sqlite if that’s what you’re after. The above example isn’t relevant to your situation unless you’re using Couchdb. Maybe this example can help: Save conversation sqlite

Topic		Replies	Views
Conversation was disappeared after refreshing the page Rasa Open Source	21	2336	April 8, 2019
How to access conversations stored in Inmemory tracker store of rasa? Rasa Open Source	4	1526	February 14, 2023
Track and load previous conversation Rasa Open Source	3	620	August 15, 2018
Tracker store setup Rasa Open Source	7	2108	June 26, 2019
Conversations not stored in the tracker store Rasa Open Source	1	530	December 16, 2019

Can the tracker recover conversations after a server restart?

Related Topics