generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 68
Open
Description
@awsapm can you deep dive into this problem?
Summary
Your pet clinic chatbot is recommending nutrition products for pets that don't exist in your nutrition service database.
Key Findings:
High 404 Error Rate - The nutrition service shows 247 requests returning 404 (Not Found) status over the last 4 hours
Agent Behavior Pattern - The pet clinic agent calls the nutrition service, gets 404 responses, but still generates product recommendations anyway
Service Flow Issue - The dependency chain shows: pet clinic agent → nutrition service → 404 response → agent still provides recommendations
Root Cause: The pet clinic agent is hallucinating nutrition product recommendations. When the nutrition service returns 404 for a pet type (indicating no nutrition data exists for that animal), the agent doesn't have actual product data but generates recommendations anyway.
Next Steps:
Configure agent validation - Update the pet clinic agent to handle 404 responses properly and inform customers when nutrition products aren't available for specific pet types
Expand nutrition database - Add nutrition data for the missing pet types that customers are asking about
Implement fallback responses - Configure the agent to provide appropriate responses when nutrition data isn't available rather than hallucinating products
The issue is clearly a service behavior problem where the agent is generating recommendations not based on actual service data.
Metadata
Metadata
Assignees
Labels
No labels