I’m wondering if someone could tell me how to handle the following scenario.
I have a slow running FormValidationAction function and want to use twilio for incoming and outgoing messages.
I noticed that when i send the message via twilio, rasa server acknowledges the message and then kicks off the the action handler. Then after ~12 secs twilio sends a FIN/ACK to the rasa server. The rasa server replies with a FIN/ACK to twilio, and then also sends a FIN/ACK to the action server - assuming things are taking too long and closes everything down.
The action server then finishes it’s job ~30 secs, and sends the response to the rasa server, which acknowledges it with http 200, but then sends a failed RST/ACK message to action handler and also doesn’t forward the message back to twilio as that connection is closed.
I’ve looked into locks, conversation session timeouts, timeouts on rasa side but as this is initiated from twilio I don’t see how to handle this?
Also why doesn’t rasa send a message back to twilio on the output_channel - is this because whilst it receives the response from the action server it’s basically closed that session?
If an agent was writing a message reply how does this work?
Also i would like to send a message saying “Processing..” but this uttermessage is only sent once the FormValidationAction completes so is there is no asynchronous message response?
Perhaps someone can explain how this pattern should be handled as I couldn’t see any documentation or video to handle this.