error-troubleshooting

Diagnose and resolve common Kailash SDK workflow, runtime, and DataFlow errors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Kailash SDK developers frequently hit recurring errors such as Nexus blocking in Docker, missing .build() calls, wrong connection parameter order, cycle convergence failures, and DataFlow template syntax mistakes. This Skill maps each symptom to its root cause and provides a verified fix. ## Core Features & Use Cases - Symptom-to-Fix Lookup: A quick reference table maps symptoms like "API hangs forever" or "TypeError: expects Workflow" directly to the correct solution. - Detailed Error Guides: Eight focused reference documents cover Nexus blocking, connection pool exhaustion, connection parameters, cycle convergence, DataFlow templates, missing .build(), parameter validation, runtime execution, and v1.0 migration errors. - Prevention Checklist: A pre-run checklist helps developers avoid the most common mistakes before executing workflows. - Use Case: When a FastAPI deployment hangs on startup, the Skill identifies the Nexus auto_discovery conflict with DataFlow and provides the corrected initialization order. ## Quick Start Ask the assistant to troubleshoot why your Kailash workflow fails with a specific error message or symptom, such as a hanging Nexus server or a missing required parameter error.

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 fail with 'WorkflowBuilder has no attribute execute'?▼

This error means you forgot to call .build() before execution. The correct pattern is runtime.execute(workflow.build()), since WorkflowBuilder must be compiled into a Workflow before the runtime can execute it.

How do I fix Nexus hanging or blocking in Docker or FastAPI?▼

Nexus blocks when LocalRuntime is used in async containers or when auto_discovery conflicts with DataFlow. Use AsyncLocalRuntime and create Nexus with auto_discovery=False, then register workflows manually with app.register().

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

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

Why does my workflow connection fail with 'target node not found'?▼

This usually means the add_connection parameters are in the wrong order. The correct 4-parameter order is from_node, from_output, to_node, to_input, and nested outputs require dot notation such as result.filters.

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

No, DataFlow nodes do not accept {{}} templates and will raise errors like invalid literal for int(). Use explicit workflow connections to pass values between nodes, which preserves Python type safety.

Why does my cyclic workflow run forever without converging?▼

Cycles fail to converge when the convergence criteria uses nested paths or when no max_iterations limit is set. Use flattened field names in converge_when(), always set max_iterations, and provide initial parameters for the first iteration.