Overview
Diagnostics performs comprehensive checks across all app components—agents, tools, events, memory, and orchestration logic. It automatically detects missing or misconfigured elements and prioritizes issues for efficient remediation.Running Diagnostics
- Navigate to your app’s Overview page.
- Click Run Diagnostics.
- Wait for the scan to complete.
- Review the diagnostic report.
What Gets Checked
| Category | Checks |
|---|---|
| Agents | Configuration completeness, tool linkages, knowledge connections, instruction quality, deprecated bindings |
| Tools | Workflow tool deployment status, code tool syntax errors, MCP server connectivity, parameter validation, missing dependencies |
| Events | Event trigger configuration, workflow bindings, parameter mappings, handler assignments |
| Knowledge | Search AI application links, index status, connector health, data freshness |
| System | Graph compilation, LLM configuration, orchestration logic, environment variables |
Diagnostics performs static and logical validation. It evaluates configuration health. Use Playground to test conversational outcomes.
Report Structure
Severity Levels
| Level | Icon | Meaning |
|---|---|---|
| Error | 🔴 | Critical issue preventing deployment |
| Warning | 🟡 | Potential problem that should be addressed |
| Info | 🔵 | Informational note or suggestion |
Report Views
Overview Tab: High-level summary┌──────────────────────────────────────────────────┐
│ Diagnostics Report │
├──────────────────────────────────────────────────┤
│ │
│ Status: ⚠️ Issues Found │
│ │
│ 🔴 Errors: 2 │
│ 🟡 Warnings: 3 │
│ 🔵 Info: 5 │
│ │
└──────────────────────────────────────────────────┘
Agents Tab: Agent-specific issues
┌────────────────────────────────────────────────────┐
│ Agents │
├────────────────────────────────────────────────── ─┤
│ │
│ Support Agent │
│ 🔴 Missing tool: get_order_status (not deployed) │
│ 🟡 Knowledge source ‘faq_db’ index is stale │
│ [Fix now] │
│ │
│ Billing Agent │
│ ✅ No issues found │
│ │
└────────────────────────────────────────────────────┘
Tools Tab: Tool-specific issues
┌────────────────────────────────────────────────────┐
│ Tools │
├────────────────────────────────────────────────────┤
│ │
│ Workflow Tools │
│ 🔴 process_refund: Not deployed │
│ [Deploy now] │
│ │
│ MCP Tools │
│ 🟡 crm_tools: Server connection timeout │
│ Last successful connection: 2 hours ago │
│ [Test connection] │
│ │
│ Code Tools │
│ ✅ All code tools validated │
│ │
└────────────────────────────────────────────────────┘
Common Issues
Missing Tool Deployment
Stale Knowledge Index
Missing Environment Variables
MCP Server Unreachable
Agent Without Tools
Quick Fixes
Many issues include a [Fix now] button:| Issue | Quick Fix Action |
|---|---|
| Tool not deployed | Opens deployment dialog |
| Stale index | Triggers reindexing |
| Missing link | Opens configuration page |
| Invalid config | Opens editor with issue highlighted |
Validation Rules
Diagnostics applies consistent standards:Agents Must Have
- ✅ Name and description
- ✅ At least one capability (tools or knowledge)
- ✅ Valid AI model configured
- ✅ All linked tools deployed
Tools Must Have
- ✅ Name and description
- ✅ Valid parameter definitions
- ✅ Successful test execution
- ✅ Deployed status (for workflow tools)
Events Must Have
- ✅ Trigger condition defined
- ✅ Handler workflow linked
- ✅ Parameters mapped correctly
Best Practices
Run Before Every Deployment
Make diagnostics part of your deployment checklist:Address Warnings
While warnings don’t block deployment, they often indicate issues that will affect users.Regular Health Checks
Run diagnostics periodically, not just before deployment:- Catch configuration drift.
- Detect external service issues.
- Maintain system health.
Limitations
Diagnostics performs static and logical validation only:| Checks | Doesn’t Check |
|---|---|
| Configuration completeness | Conversation quality |
| Tool connectivity | Response accuracy |
| Dependency resolution | User satisfaction |
| Syntax validation | Edge case handling |