Skip to main content

Documentation Index

Fetch the complete documentation index at: https://koreai.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Validate your app’s health and readiness before deployment.

​
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. 
Run Diagnostics → Scan Configuration → Identify Issues → Generate Report → Fix Issues

​
Running Diagnostics

  1. Navigate to your app’s Overview page.
  2. Click Run Diagnostics.
  3. Wait for the scan to complete.
  4. Review the diagnostic report.

​
What Gets Checked

CategoryChecks
AgentsConfiguration completeness, tool linkages, knowledge connections, instruction quality, deprecated bindings
ToolsWorkflow tool deployment status, code tool syntax errors, MCP server connectivity, parameter validation, missing dependencies
EventsEvent trigger configuration, workflow bindings, parameter mappings, handler assignments
KnowledgeSearch AI application links, index status, connector health, data freshness
SystemGraph 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

LevelIconMeaning
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

🔴 Error: Tool 'get_order_status' is not deployed

Agent 'Support Agent' references this tool but it hasn't been
deployed. The agent won't be able to invoke it.

Fix: Navigate to Tools → get_order_status → Deploy

​
Stale Knowledge Index

🟡 Warning: Knowledge source 'product_catalog' index is stale

Last indexed: 7 days ago
Source last updated: 2 days ago

Some responses may use outdated information.

Fix: Navigate to Knowledge → product_catalog → Reindex

​
Missing Environment Variables

🔴 Error: Environment variable 'API_KEY' is not set

Tool 'external_api_call' requires this variable but it's
not configured in the current environment.

Fix: Navigate to Settings → Environment → Add variable

​
MCP Server Unreachable

🟡 Warning: MCP server 'enterprise_tools' is unreachable

Connection attempts failed for the past 15 minutes.
Tools from this server won't be available.

Fix: Check server status or update connection settings

​
Agent Without Tools

🔵 Info: Agent 'FAQ Agent' has no tools configured

This agent can only use knowledge retrieval and won't be
able to take actions. This may be intentional for
information-only agents.

​
Quick Fixes

Many issues include a [Fix now] button:
IssueQuick Fix Action
Tool not deployedOpens deployment dialog
Stale indexTriggers reindexing
Missing linkOpens configuration page
Invalid configOpens 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: 
Pre-deployment:
1. [ ] Run diagnostics
2. [ ] Fix all errors
3. [ ] Review warnings
4. [ ] Create version
5. [ ] Deploy to staging
6. [ ] Test in staging
7. [ ] Deploy to production

​
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:
ChecksDoesn’t Check
Configuration completenessConversation quality
Tool connectivityResponse accuracy
Dependency resolutionUser satisfaction
Syntax validationEdge case handling
For conversation testing, use the Playground feature to simulate real interactions.