Reference
Troubleshooting
Use these troubleshooting patterns to narrow down whether a Calypso RAG problem comes from keys, indexing, policy, grounding, or the deployment surface.
Start with the layer that failed
Most Calypso RAG issues become easier to solve when you identify the failing layer first:
- key and authorization
- knowledge readiness
- agent policy
- Playground validation
- integration wiring
- post-launch widget outcomes
Playground cannot send
Check:
- an active project API key exists
- the correct key is selected
- the selected key still belongs to the current project
The answer is weak or ungrounded
Check:
- whether the source is truly indexed
- whether the source pool is too broad or too weak
- whether the selected profile is the one you intended
- whether the answer returned sources, hid them, or never grounded at all
A named profile is not behaving as expected
Check:
- the exact model ID being called
- whether the profile still exists
- whether the intended profile has different scope or presentation settings than the default agent
The widget is live but answers do not match Playground
Check:
- whether the widget is using linked-agent mode
- which agent is actually bound to the widget
- whether the default agent or a named profile was intended
Analytics are empty
Check:
- whether the selected team is correct
- whether the widget has enough activity for the selected range
- whether you are expecting analytics from a non-widget surface that is not represented here yet
Best escalation path
When in doubt:
- validate the same behavior in Playground
- confirm the agent policy in Agent Builder
- confirm source readiness in Knowledge
- only then debug the integration surface