error-troubleshooting

Diagnose Kailash SDK workflow, runtime, and DataFlow errors.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/myeohVmzrka92/disease-risk-controller-S2 --skill error-troubleshooting-myeohvmzrka92
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-troubleshooting
Source: https://github.com/myeohVmzrka92/disease-risk-controller-S2/tree/main/.claude/skills/31-error-troubleshooting
Command: npx skills add https://github.com/myeohVmzrka92/disease-risk-controller-S2 --skill error-troubleshooting-myeohvmzrka92

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly diagnose and resolve recurring Kailash SDK failures that interrupt workflow execution, integration, and deployment, especially when errors are hard to trace from stack traces alone.

Core Features & Use Cases

  • Workflow execution fixes: Resolves missing build calls, incorrect runtime usage, and failed execution patterns.
  • Connection and parameter debugging: Identifies wrong connection ordering, missing inputs, and validation failures.
  • Integration troubleshooting: Covers Nexus blocking, DataFlow template syntax issues, cycle convergence problems, and runtime-specific edge cases.
  • Use case: A developer sees a failing workflow in FastAPI, a hanging Nexus startup, or a connection mapping error and uses this Skill to isolate the root cause and apply the correct Kailash pattern.

Quick Start

Ask the assistant to diagnose the Kailash error message you are seeing and return the exact corrective pattern for workflow building, runtime execution, parameter passing, connections, or cycle convergence.

Frequently Asked Questions about error-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Kailash Nexus startup hang or block indefinitely?

A hanging Kailash Nexus startup is typically caused by incorrect runtime selection or connection mapping mistakes. Identifying the specific startup pattern and applying the correct runtime configuration resolves the blocking behavior.

How do I fix missing build call errors in Kailash SDK workflows?

Missing build call errors in Kailash SDK workflows occur when workflow construction is incomplete. Applying the correct build pattern and verifying parameter validation ensures successful workflow execution and restores stable DataFlow operations.

How do I resolve parameter validation failures during Kailash DataFlow execution?

Parameter validation failures during Kailash DataFlow execution happen when connection ordering or inputs are missing. Correcting connection mapping and passing validated parameters resolves the execution failures.

What causes cyclic convergence problems in Kailash SDK workflows?

Cyclic convergence problems in Kailash SDK workflows arise from incorrect connection ordering and runtime edge cases. Isolating the cycle and applying documented convergence patterns restores stable workflow execution.

How do I troubleshoot DataFlow template syntax issues in Kailash?

DataFlow template syntax issues in Kailash are diagnosed by inspecting template construction and parameter passing. Correcting the syntax and validating the template pattern resolves the execution errors.

Can I use this to debug Kailash SDK errors when integrating with FastAPI?

Yes, this diagnoses Kailash SDK errors encountered during FastAPI integration, including failing workflows and connection mapping mistakes. It isolates the root cause and provides the correct Kailash pattern to restore execution.