agentleFS
terrene-foundationterrene-foundation/pact/.claude/skills/31-error-troubleshooting/SKILL.md

error-troubleshooting

Skill0 starsChanged 7 months agoApache-2.0View on GitHub

Common error patterns and troubleshooting guides for Kailash SDK including Nexus blocking issues, connection parameter errors, runtime execution errors, cycle convergence problems, missing .build() calls, parameter validation errors, and DataFlow template syntax errors. Use when encountering errors, debugging issues, or asking about 'error', 'troubleshooting', 'debugging', 'not working', 'hangs', 'timeout', 'validation error', 'connection error', 'runtime error', 'cycle not converging', 'missing build', or 'template syntax'.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check logs, validate inputs, test nodes individually, add LoggerNode for visibility

    line 31
  2. Distinctive:

    All connections use 4 parameters?

    line 68
  3. Distinctive:

    All required node parameters provided?

    line 69
  4. Very specific:

    Always: check .build() was called

    line 79
  5. Distinctive:

    Always: verify absolute imports when seeing import errors

    line 81

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Kailash Error Troubleshooting

Common error patterns and solutions for Kailash SDK.

Sub-File Index

Critical Errors

  • error-nexus-blocking - Nexus hangs or blocks
    • Symptom: API hangs forever | Cause: LocalRuntime in Docker/async | Fix: Use AsyncLocalRuntime
  • error-missing-build - Forgot .build()
    • Symptom: TypeError: execute() expects Workflow, got WorkflowBuilder | Fix: runtime.execute(workflow.build())

Connection & Parameter Errors

  • error-connection-exhaustion - Database connection exhaustion
    • Symptom: "too many connections" | Fix: Use external_pool parameter, set max_pool_size = DB max / worker count
  • error-connection-params - Invalid connections
    • Symptom: Node gets wrong data | Fix: Use 4-param format (source_id, source_param, target_id, target_param)
  • error-parameter-validation - Invalid node parameters
    • Symptom: ValidationError: Missing required parameter | Fix: Check node docs for required params

Runtime & Cycle Errors

  • error-runtime-execution - Runtime failures
    • Check logs, validate inputs, test nodes individually, add LoggerNode for visibility
  • error-cycle-convergence - Cycles don't converge
    • Symptom: Infinite loop / max iterations exceeded | Fix: Add cycle_complete convergence check

DataFlow Errors

  • error-dataflow-template-syntax - Template string errors
    • Symptom: SyntaxError in template strings | Fix: Use {{variable}} syntax

Kaizen Provider Errors

  • error-kaizen-provider-config - Provider configuration issues
    • Azure 400 "messages must contain 'json'" | Use json_prompt_suffix() or set response_format
    • "Missing required parameter: response_format.type" | Don't put api_version in response_format
    • DeprecationWarning about provider_config | Migrate to response_format field
    • Azure env var deprecation warnings | Switch to canonical names (AZURE_ENDPOINT, AZURE_API_KEY)

Quick Error Reference

SymptomError TypeQuick Fix
API hangs foreverNexus blockingUse AsyncLocalRuntime
TypeError: expects WorkflowMissing .build()Add .build() call
Node gets wrong dataConnection paramsCheck 4-parameter format
ValidationErrorParameter validationCheck required params
Infinite loopCycle convergenceAdd convergence condition
Template SyntaxErrorDataFlow templateUse {{variable}} syntax
Runtime failsRuntime executionCheck logs, validate inputs
"too many connections"Connection exhaustionUse external_pool injection
Azure 400 "messages must contain 'json'"Kaizen providerUse json_prompt_suffix() or response_format
"Missing required parameter: response_format.type"Kaizen providerDon't put api_version in response_format
DeprecationWarning about provider_configKaizen providerMigrate to response_format field

Error Prevention Checklist

  • Called .build() on WorkflowBuilder?
  • Using AsyncLocalRuntime for Docker/async?
  • All connections use 4 parameters?
  • All required node parameters provided?
  • Cyclic workflows have convergence checks?
  • Template strings use {{variable}} syntax?
  • Using external_pool in multi-worker deployments?
  • Structured output in response_format (not provider_config)?
  • Azure using canonical env vars (AZURE_ENDPOINT, AZURE_API_KEY)?
  • structured_output_mode="explicit" for new agents?

Debugging Tips

  1. Always check .build() was called
  2. Never ignore connection validation errors
  3. Always verify absolute imports when seeing import errors
  4. Never assume mock tests found real issues -- use real infrastructure

Related Skills

  • 16-validation-patterns - Validation patterns
  • 17-gold-standards - Best practices to avoid errors
  • 01-core-sdk - Core patterns
  • 02-dataflow - DataFlow specifics
  • 03-nexus - Nexus specifics

Support

  • pattern-expert - Pattern validation
  • gold-standards-validator - Check compliance
  • testing-specialist - Test debugging

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.