Tencent/WeKnora · error

no schema info found

Error message

no schema info found

What it means

DataSchema tool iterated the knowledge's chunks but never found both required schema chunk types (table summary and table column): the knowledge was ingested without table-structure extraction, so there is no stored schema to report and the tool aborts with a failure result.

Source

Thrown at internal/agent/tools/data_schema.go:123

			Success: false,
			Error:   fmt.Sprintf("Failed to list chunks for knowledge ID '%s': %v", input.KnowledgeID, err),
		}, err
	}

	var summaryContent, columnContent string
	for _, chunk := range chunks {
		if chunk.ChunkType == types.ChunkTypeTableSummary {
			summaryContent = chunk.Content
		} else if chunk.ChunkType == types.ChunkTypeTableColumn {
			columnContent = chunk.Content
		}
	}

	if summaryContent == "" || columnContent == "" {
		return &types.ToolResult{
			Success: false,
			Error:   fmt.Sprintf("No table schema information found for knowledge ID '%s'", input.KnowledgeID),
		}, fmt.Errorf("no schema info found")
	}

	output := fmt.Sprintf("%s\n\n%s", summaryContent, columnContent)

	return &types.ToolResult{
		Success: true,
		Output:  output,
		Data: map[string]interface{}{
			"summary": summaryContent,
			"columns": columnContent,
		},
	}, nil
}

View on GitHub (pinned to 988cbb0330)

Solutions

  1. Re-ingest the source file with table parsing enabled so TableSummary/TableColumn chunks are produced
  2. Confirm the uploaded file actually contains a parseable table
  3. Check chunk listing succeeded and chunks were not filtered by enabled flag
Defensive patterns

Strategy: validation

When it happens

Trigger: Thrown at internal/agent/tools/data_schema.go:123 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of Tencent/WeKnora@988cbb0330 (2026-09-02). Data as JSON: /api/errors/13944ce73c907edd. Report an issue: GitHub.