Chatbot agent fails to generate new agent session after EOS signal
On initial start the agent is authenticating fine, subscribing to messages fine, responding fine, until it seemingly out of nowhere receives an EOS signal with the reason 'unexpected session state'.
This is happening at random intervals, aswell as at different uptimes, and different lengths of downtime between unique chats.
Upon receiving the EOS signal, the agent attempts to generate a new agent session using the query below, however it does not seem to get a valid response unlike on the initial start.
Query:
These are the logs, which includes the last successful message sent, aswell as the error thrown when attempting to start a new agent session:
2020-09-21T15:41:29.192137+00:00 app[web.1]: [sendMessage] Successfully sent message to visitor
2020-09-21T16:12:40.477297+00:00 app[web.1]: [data] Received EOS signal. Starting a new agent session.
2020-09-21T16:12:40.478344+00:00 app[web.1]: { reason: 'unexpected session state', sig: 'EOS' }
2020-09-21T16:12:40.478668+00:00 app[web.1]: [startAgentSession] Request sent
2020-09-21T16:12:41.674697+00:00 app[web.1]: [startAgentSession] Request fail
2020-09-21T16:12:41.674738+00:00 app[web.1]: {"errors":[{"UUID":"060faba6-6f06-4188-b698-e3b3627c00a0","locations":[
{"line":2,"column":9}],"message":"failed to create new session","name":"GRAPHQL_EXEC_ERROR","path":["startAgentSession"]}
],"data":null}
I'm hoping to get some help on this issue.
Thanks in advance!
-
Hey Shawn,
It looks like you haven't received a response on this post so I wanted to see if you're still experiencing issues on your end. My knowledge in this area is rather limited so I'll most likely need to create a ticket on your behalf to troubleshoot further.
Let me know!
Por favor, entrar para comentar.
1 Comentários