error-troubleshooting

Diagnose Kailash SDK failures by mapping symptoms to root-cause fixes.

Updated Oct 10, 2025
One-click install
npx skills add https://github.com/FFOO6866/lead2cash --skill error-troubleshooting-ffoo6866
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-troubleshooting
Source: https://github.com/FFOO6866/lead2cash/tree/main/.claude/skills/31-error-troubleshooting
Command: npx skills add https://github.com/FFOO6866/lead2cash --skill error-troubleshooting-ffoo6866

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly diagnose and resolve common Kailash SDK failures across workflow building, execution, connections, cycle convergence, DataFlow templating, and Kaizen provider configuration (especially Azure structured output).

Core Features & Use Cases

  • Targeted error matching: Maps frequent symptoms (e.g., hangs, validation failures, missing build, connection mistakes, infinite cycles, template syntax errors) to the most likely root cause and a specific fix.
  • Operational troubleshooting playbook: Provides checklists and debugging steps to confirm the failing phase (build vs runtime vs parameter wiring) and prevent recurrence.
  • Provider-specific remedies: Covers Kaizen/Azure issues such as json_object prompt requirements, response_format vs provider_config separation, deprecation warnings, and canonical Azure environment variables.

Quick Start

Use the error-troubleshooting skill when you see a Kailash failure message (like a workflow hang, a .build()-related execution error, a connection parameter order issue, a cycle not converging error, a DataFlow {{}} template syntax error, or an Azure 400 structured output error) and want the most likely fix immediately.

Frequently Asked Questions about error-troubleshooting

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

FAQPage Schema
Why does my Kailash workflow hang during execution?

Kailash workflow hangs often stem from missing `.build()` calls or incorrect 4-parameter connection wiring. Apply targeted error matching to identify the failing phase and execute the corresponding root-cause fix to resume execution.

How do I fix a cycle convergence failure in Kailash?

Fix Kailash cycle convergence failures by validating your convergence criteria and adjusting iteration parameters. Troubleshooting playbooks map this symptom to specific root causes and provide prescriptive checks to prevent infinite cycles.

What causes Azure structured output 400 errors in Kaizen?

Azure structured output 400 errors in Kaizen usually occur when `json_object` prompt requirements are missing or `response_format` and `provider_config` are improperly separated. Apply provider-specific remedies using canonical Azure environment variables.

How do I resolve DataFlow template syntax errors?

Resolve DataFlow template syntax errors by enforcing proper `{}`-style template rules for the correct subsystem. Error matching maps `{{}}` syntax mistakes to specific fixes for the right DataFlow template configuration.

How do I validate Kailash SDK connection parameters?

Validate Kailash SDK connection parameters by confirming correct 4-parameter connection usage and checking parameter order during the build phase. Operational troubleshooting checklists help isolate wiring mistakes from runtime failures.

What is the best way to debug Kailash workflow execution problems?

Debug Kailash workflow execution problems by identifying whether the failure occurs at build, runtime, or parameter wiring. Targeted error matching maps symptoms like missing builds and validation failures directly to specific root-cause fixes.