What problem does it solve?
Dagster pipeline failures—including asset materialization errors, sensor malfunctions, partition issues, and connection problems with integrated services like S3, Milvus, and rclone—cause costly downtime for AI infrastructure stacks and require hours of manual troubleshooting to resolve.
Core Features & Use Cases
- Direct Instance Inspection: Uses Dagster MCP tools to pull run logs, asset status, and error details directly from the running Dagster instance, eliminating the need to manually navigate the UI.
- Infrastructure Troubleshooting: Provides step-by-step guidance to fix connection and configuration issues for core services including S3/MinIO, Milvus, MongoDB, rclone, and NATS.
- Pre-Defined Error Fixes: Includes solutions for common failure patterns like partition stuck states, embedding failures, document parsing errors, and IO manager type mismatches.
- Use Case: If your document ingestion pipeline fails due to a Milvus connection timeout, this skill walks you through verifying Milvus is running, checking embedding dimension settings, and re-triggering the failed asset run.
Quick Start
Use the debug-pipeline skill to investigate why your document ingestion asset is failing to materialize and resolve the root cause.