error-troubleshooting

Diagnose and resolve common Kailash SDK runtime, connection, and validation errors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Kailash SDK workflows fail with recurring errors like Nexus blocking, missing .build() calls, connection parameter mistakes, and cycle convergence failures, and developers waste time hunting for fixes across scattered documentation. ## Core Features & Use Cases - Symptom-to-Fix Mapping: A quick reference table maps symptoms like "API hangs forever" or "TypeError: expects Workflow" directly to root causes and fixes. - Detailed Error Guides: Eight focused guides cover Nexus blocking, missing .build(), connection parameters, parameter validation, runtime execution, cycle convergence, DataFlow template syntax, and v1.0 migration errors. - Use Case: Your FastAPI deployment hangs on startup after integrating DataFlow with Nexus. Consult the Nexus blocking guide to learn that auto_discovery must be disabled and AsyncLocalRuntime used, reducing startup to under 2 seconds. ## Quick Start Ask the AI to diagnose why your Kailash workflow throws "TypeError: execute() expects Workflow" and apply the recommended fix.

Frequently Asked Questions about error-troubleshooting

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

FAQPage Schema
How do I fix 'TypeError: execute() expects Workflow' in Kailash?▼

This error means you forgot to call .build() on the WorkflowBuilder before execution. Change runtime.execute(workflow) to runtime.execute(workflow.build()) so the runtime receives a compiled Workflow instead of a builder.

Why does Nexus hang or block on startup with DataFlow?▼

Nexus blocks because auto_discovery=True triggers synchronous workflow execution during DataFlow model registration. Create Nexus with auto_discovery=False, register workflows manually with app.register(), and startup completes in under 2 seconds.

How do I fix 'too many connections' errors in multi-worker deployments?▼

Connection exhaustion happens when each Gunicorn worker creates its own database pool. Create one pool at app startup and pass it via the external_pool parameter, sizing max_pool_size as database max connections divided by worker count.

What is the correct connection syntax for Kailash workflows?▼

Use the 4-parameter form: add_connection(from_node, from_output, to_node, to_input). For nested outputs use dot notation like "result.filters". The deprecated 3-parameter syntax causes 'node not found' errors.

Why does my cyclic workflow run forever without converging?▼

Cycles fail to converge when convergence criteria use nested paths or max_iterations is unset. Use flattened field names in converge_when("done == True"), always set max_iterations, and provide initial parameters for the first iteration.

Does DataFlow support {{}} template syntax for parameters?▼

No, DataFlow nodes expect native Python types and reject {{}} templates with errors like "invalid literal for int()". Pass dynamic values through explicit workflow connections instead, which preserves type safety.