Bot routing in QnA exits even without the user typing exit

Please review the following checkpoints to help resolve the issue.

1.Check the Conversation Path Setup in Lex v2:

• In the Lex v2 console, open your specialty bot’s intent.
• Inspect the Fulfillment and Next step configurations.
• Ensure that after Lambda fulfillment, the "next step" is set to elicit another intent, slot, or take further user input—not set to close the conversation or return.

2.Review Lambda Function Response:

• Your Lambda should not return a "close" dialog action unless you intend the session to end.
• Instead, return a "delegate" or "elicitSlot" directive if you want the conversation to continue.

3.Conditional Branching:

• If using conditional branches, make sure none are automatically defaulting to a closing response once Lambda finishes1.
• Map each scenario to the appropriate next step, so the routing persists until the user explicitly exits.

Please also refer to the following documentation.

• https://docs.aws.amazon.com/lexv2/latest/dg/paths-nextstep.html
• https://docs.aws.amazon.com/lexv2/latest/dg/building-paths.html
• https://docs.aws.amazon.com/lexv2/latest/dg/paths-branching.html