- Newest
- Most votes
- Most comments
You're correct that this is a new feature for Amazon Bedrock Flows, and your understanding of the multi-turn conversation capability with agent nodes is accurate. However, the issue you're experiencing with the agent conversation being interrupted is due to the flow structure you've created.
In your current flow, each user response is indeed being sent back through the classifier prompt and condition node. This is why you're seeing the agent's conversation potentially interrupted when a user response triggers a different condition.
For a call center AI or similar application where you want to maintain a continuous conversation with an agent, this flow structure is not ideal. Instead, you should consider a more customized approach that allows the agent node to maintain control of the conversation once it's initiated.
Here's a suggested approach to improve your flow:
-
Keep your initial classifier prompt and condition node.
-
When Condition A is met (triggering the agent conversation), create a separate branch of the flow dedicated to the agent interaction.
-
In this agent branch, use a loop or recursive structure that allows the agent to continue the conversation without going back through the classifier each time.
-
Implement a mechanism within the agent conversation to determine when the interaction is complete. This could be based on the agent gathering all necessary information or the user indicating they're done.
-
Only after the agent conversation is complete should the flow return to the main branch or end.
For Conditions B and C, you can keep your current structure of directing to specific prompts.
This approach will allow the agent to maintain an uninterrupted multi-turn conversation when needed, while still providing the flexibility to handle other types of inquiries with different prompts.
Remember, as this is a preview feature, its capabilities and best practices may evolve. It's a good idea to keep an eye on AWS documentation and updates for any changes or improvements to the multi-turn conversation feature in Amazon Bedrock Flows.
Sources
Introducing multi-turn conversation with an agent node for Amazon Bedrock Flows (preview) | AWS Machine Learning Blog
Converse with an Amazon Bedrock flow - Amazon Bedrock
Node types in flow - Amazon Bedrock
Relevant content
asked 2 years ago
asked 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 7 months ago

In a multi turn conversation how do I know that the agent will continue the conversation or he will terminate it? Can I adjust that in order to complete the conversation when I desire?