- Newest
- Most votes
- Most comments
The latency you're seeing makes no sense. I get around 250 ms with NOT a yes/no bot. Any chance you Connect, Lex and lambda are in different regions or something like that? If you build a bot from scratch with no real configuration does it show the same latency?
david
Hello,
Thanks for your response. All our resources are in us-west-2. Normally it takes 2-3 seconds, but sometimes it is peaking as you can see. And user on the call waits. We don't have this issue on chat. Only on voice channel.. I tested from Lex console as well. Its response is about 2 seconds.
Thank you
Amazon Lex bots will have a cold start after 24 hours with no traffic. Check if this is the case, if it is then you can prevent this by scheduling a Lambda function to make a call to Lex every few hours (you can use Eventbridge for this). A simple PostText (Lex v1) should be fine for this purpose.
Relevant content
- asked 5 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- How do I set up logging for Amazon Pinpoint voice messages for Amazon Pinpoint SMS and Voice v1 API?AWS OFFICIALUpdated 2 years ago