error-troubleshooting

Missing .build() calls cause runtime execution failures in Kailash workflows. Always invoke .build() on your workflow object before passing it to runtime.execute(). This compiles and validates the workflow structure, ensuring all components and connections are properly initialized before execution.

Nexus blocking occurs when component dependencies create deadlocks or when connections aren't properly configured. Verify connection parameters between components, ensure all required parameters are validated, and check that DataFlow templates have correct syntax. Review your workflow graph for circular dependencies or missing data paths.

Parameter validation errors arise from mismatched or missing input values to workflow components. Check that all required parameters are supplied with correct types, verify connection parameters match component specifications, and consult the Kailash documentation for component-specific requirements. Use the error message to identify which parameter failed validation.

Runtime failures in DataFlow workflows typically stem from missing .build() calls, incorrect connection parameters, cycle convergence issues, or syntax errors in templates. Diagnose by checking template syntax, validating all connections between components, ensuring cycle convergence logic is correct, and confirming parameters are properly initialized before execution.

Yes, Kailash SDK supports cross-component integrations between Nexus and DataFlow within unified workflows. Ensure all inter-component connections are correctly configured, parameter types align across framework boundaries, and the entire workflow is built before execution to validate the integration.

Start by verifying your workflow calls .build() before runtime.execute(), check all connection parameters are correctly specified, validate that required parameters are supplied, and review DataFlow template syntax for errors. These account for the majority of SDK errors and are quickest to resolve.