Hi, We have RASA deployed on multiple instances and based on the documentation, a unique session id has to be created at the start of the conversation and pass the session id to rasa, until the conversation with the end user is done.
To my understanding the session is persisted IN Memory with in the RASA Instance. What will happen if the load balancer sends the same user request to a different RASA Instance instead of sending it to the instance where the session is created and persisted. We are using the “/trigger_intent” end point as we are doing NLP /Intent prediction outside RASA. We are cacheing the slots and sending them as part of every request.
Does RASA Core use the the tracker events history to predict the next action? . If RASA core uses tracker events to predict the next action , we have to sync the session across all the instances, so we wanted to know how it works behind the scene. As of now we are not sending the tracker events history, when the call goes to a different instance where does not have session.