1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
I have a similar problem...I think. The first call of the day which is answered by Lex, hears nothing for 2-3 seconds before Lex starts talking. I have this problem every day. Subsequent calls are ok.
con risposta 2 anni fa
Contenuto pertinente
AWS UFFICIALEAggiornata 2 anni fa- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
Luc, just curious if you ever were able to resolve this? I experience the same thing for Lex V2 answering first call of day it seems like. I’ve implemented Provisioned Concurrency for my webhook Lambda that handles my Lex interactions to see if it was a cold start Lambda, but even with Provisioned Concurrency I experience 4-5 second response from Lex on that opening call of the day (and I’m not using a delayed session attribute timing setting).