Schema Source Configuration
”Provide either schema_file or mcp_server_url”
This error occurs when neither a local schema file nor an MCP server URL is configured. Tasks that require function schemas (such asdata-generate, schema-polish, and schema-triggered-patch) need at least one schema source.
Solution: Configure a schema source using /configure:
”Schema source fields are mutually exclusive”
This error occurs when bothschema_file and mcp_server_url are provided in an /execute config file. You must choose one.
Solution: Remove one of the two fields from your configuration file, keeping only the schema source you want to use.
/execute Errors
”Missing required field: task”
Your/execute configuration file does not include a task field.
Solution: Add a task field to your YAML config. Supported values: data-generate, data-repair, data-audit, schema-polish, resample, schema-triggered-patch.
”Unknown fields in config”
Your configuration file contains fields not recognized for the specified task. Solution: Check the task’s documentation for supported parameters and remove any unrecognized fields. Each task type accepts a different set of parameters.”Only .yaml/.yml files are supported for /execute”
The/execute command only accepts YAML files.
Solution: Ensure your config file has a .yaml or .yml extension.
Viewer Issues
”Outputs directory does not exist”
The/view command cannot find the outputs/ directory in your configured workspace.
Solution: Ensure your workspace path is correctly set (see Getting Started for initial setup) and that you have run at least one task that produces output:
{eigendata_db_path}/outputs/. This directory is created automatically when you run your first task.