How to get out of the RETRY loop for Lex Slot Confirmation

Question

I have set RETRY for my slot to 2...it goes through but if I say NO to the value it still goes back to the the beginning slot fill for the same intent. I want to branch out to another intent but I just don't see where I can detect or specify to branch when its through its alloted Retry prompts.

Dons
a year ago
note it does the correct number of retry's but after its done it starts again..where can I tell it to go to another intent after x retry's are negative

Dons · Accepted Answer

So I finally figured out the flow of this. Simple Bot with one intent and one slot variable. Enable confirmations and decline, null the slot variable and go to initial response.  That is how that loop works.

I then added my "decline counter" lambda at Initial Response and had it direct to a new intent I added called TooManyAttempts if it hit my limit of retry's.

For what its worth, this simple flow is a classic example of how things are often way too messy, difficult and not well documented in the AWS world.  IMHO

Daher · Answer

To handle the RETRY loop in Amazon Lex when a slot confirmation fails:

1. **Use Conditional Branching:** After the RETRY attempts are exhausted, you can define a condition in your Lex bot to branch out to a different intent or message. This is done using **Lambda function hooks** or **conditional checks** within your Lex bot's flow.

2. **Configure Fallback Intent:** You can also configure a fallback intent that triggers when the maximum retries are reached. This allows you to direct the conversation to a different flow or provide an alternative response.

For detailed steps, refer to the [Amazon Lex Slot Types Documentation](https://docs.aws.amazon.com/lex/latest/dg/howitworks-slots.html) and [Fallback Intent Documentation](https://docs.aws.amazon.com/lex/latest/dg/intent-fallback.html).

I hope this helps! 😁

How to get out of the RETRY loop for Lex Slot Confirmation

Add your answer

Relevant content