Troubleshooting
The fastest way to debug Jardine is to check one layer at a time. Start with the layer closest to the issue you can see.
1. Answers Are Wrong or Generic
Start with source material:
- Are the right docs active?
- Are policies clear?
- Are conflicting docs removed?
Then re-test in Tools Playground.
2. Channel Is Connected but Messages Do Not Arrive
Treat this as channel wiring first:
- Is webhook/trigger/forwarding complete?
- Is signature/secret correct?
- Is workspace/domain mapping correct?
3. Draft Exists but No Reply Is Sent
Check:
- Send settings.
- Routing ownership.
- Delivery status in thread history.
4. Too Many Escalations
Most common causes:
- Broad sensitive tags.
- Strict route conditions.
- Missing account context.
- Weak source grounding.
5. Team Command Results Are Inconsistent
Check:
- Slack/Discord setup in Tools.
- Workspace mapping.
- Clarification or approval prompts in Chat with Jardine.
- Task outcomes in Control Center.
6. Connector Behavior Is Inconsistent
Check:
- Identity mapping.
- Credential health.
- Returned field quality.
- Fallback behavior when data is missing.
If Production Quality Drops
- Pause rollout expansion.
- Keep sensitive paths in review mode.
- Fix the highest-risk layer first.
- Re-test before expanding again.