I know that the answer “The session was ended because one of the component didn’t respond in a timely manner” from Dialogue has been reported several times. My problem is however slightly different from those mentioned on the forum since it only happens from time to time. In fact, I noticed that it occurs when the callback function takes too much time to do its action (when roughly over 5 seconds). This is typically the case for my radio app which is looking for info on TuneIn. Depending on the time TuneIn takes to answer, my app may or not face the issue from Dialogue.
I tried several workarounds :
- end the session at the beginning of the callback function (hermes.publish_end_session()) and then continue to run the code to play the radio
- adjust the parameters “session_timeout” and “lambda_timeout” in /etc/snips.toml (with restart of snips-dialogue service )
but none of them did solve the issue. I’m running Snips on a Voice Interaction Kit (Raspberry Pi 3 B+).
Does anybody have a clue?
Thanks and best regards