-
Notifications
You must be signed in to change notification settings - Fork 65
Description
Root Cause Analysis
The Problem: Your nutrition service database has limited product coverage, but your chatbot is trying to recommend products for exotic pets that aren't in your inventory.
Key Findings:
-
Limited Product Database: Your nutrition service only has products for these pet types:
• ✅ Available: cat, dog, bird, hamster, snake (limited)
• ❌ Missing: rabbit, exotic pets, chameleon, chinchilla, bearded dragon, serval, peacock, tortoise, hedgehog, sloth, porcupine, degu, tarantula, ferret, turtle, emu, llama, frog, raccoon, armadillo, amphibian, coatimundi -
High Error Rate: 12.41% error rate on nutrition lookups, with 8,474+ failed requests for unsupported pet types
-
Most Problematic Requests:
• Rabbit nutrition: 1,103 failed requests (highest volume)
• Exotic pets: 88+ failed requests
• Chameleon: 131 failed requests
• Chinchilla: 33 failed requests -
System Architecture Issue: Your pet clinic agent calls the nutrition agent, which then queries the nutrition service. When the service returns 404 (product not found), the agents may still generate recommendations based on their
training data rather than your actual inventory.
Recommended Solutions
Immediate Fixes:
-
Update Nutrition Database: Add products for the most requested missing pet types (rabbit, exotic pets, chameleon, etc.) or add explicit "not available" entries
-
Improve Error Handling: Modify your nutrition agent to:
• Return clear "product not available" messages instead of generating recommendations
• Suggest alternative products you do carry
• Redirect to general pet care advice when specific nutrition products aren't available -
Agent Prompt Engineering: Update your pet clinic agent's system prompt to:
• Only recommend products that exist in your database
• Check product availability before making recommendations
• Provide fallback responses for unsupported pet types
Pet clinic agents are recommending invalid nutritional products. Can you help me troubleshoot? @awsapm