Tencent/WeKnora · error
chunk %s is disabled
Error message
chunk %s is disabled
What it means
Authorization check inside authorizeChunkInSearchTargets: the chunk was successfully fetched by ID, but its IsEnabled flag is false. The server rejects disabled chunks/FAQ entries even when the caller's KB/document/tag scope would otherwise permit them — a deliberate availability gate, not a scope mismatch.
Source
Thrown at internal/agent/tools/scope_authorization.go:120
chunkService interfaces.ChunkService,
knowledgeService interfaces.KnowledgeService,
) (*types.Chunk, error) {
chunkID = strings.TrimSpace(chunkID)
if chunkID == "" {
return nil, fmt.Errorf("chunk_id is required")
}
if chunkService == nil {
return nil, fmt.Errorf("chunk service is unavailable")
}
chunk, err := chunkService.GetChunkByIDOnly(ctx, chunkID)
if err != nil || chunk == nil {
if err == nil {
err = fmt.Errorf("empty result")
}
return nil, fmt.Errorf("chunk %s not found: %w", chunkID, err)
}
if !chunk.IsEnabled {
return nil, fmt.Errorf("chunk %s is disabled", chunk.ID)
}
if !searchTargets.ContainsKB(chunk.KnowledgeBaseID) {
return nil, fmt.Errorf("knowledge base %s is not within the current Agent scope", chunk.KnowledgeBaseID)
}
allowed, err := searchTargetsAllowKnowledgeID(
ctx, searchTargets, chunk.KnowledgeID, chunk.KnowledgeBaseID, knowledgeService,
)
if err != nil {
return nil, fmt.Errorf("failed to validate chunk scope: %w", err)
}
if !allowed {
return nil, fmt.Errorf("chunk %s is not within the current @mention scope", chunk.ID)
}
return chunk, nil
}
// validateKnowledgeBaseIDsInSearchTargets rejects hallucinated, stale, or
// out-of-scope bN values after the model-context registry resolves them.View on GitHub (pinned to 988cbb0330)
Solutions
- Re-enable the chunk/FAQ entry if it should be served
- Filter disabled IDs out of requests before authorization
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at internal/agent/tools/scope_authorization.go:120 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/3505176ddd084ee9.
Report an issue: GitHub.