Tencent/WeKnora · error

FAQ entry is not accessible: %v

Error message

FAQ entry is not accessible: %v

What it means

Per-FAQ-entry authorization failed inside the concurrent worker: authorizeChunkInSearchTargets rejected the chunk ID (not found, disabled, out of KB scope, or outside @mention scope), so that FAQ entry is recorded as inaccessible in the results map rather than aborting the whole batch.

Source

Thrown at internal/agent/tools/get_document_info.go:140

	var wg sync.WaitGroup
	var mu sync.Mutex
	results := make(map[string]*docInfo)
	enabled := true

	for _, faqID := range faqIDs {
		faqID = strings.TrimSpace(faqID)
		if faqID == "" {
			continue
		}
		wg.Add(1)
		go func(id string) {
			defer wg.Done()
			chunk, err := authorizeChunkInSearchTargets(
				ctx, t.searchTargets, id, t.chunkService, t.knowledgeService,
			)
			if err != nil {
				mu.Lock()
				results["faq:"+id] = &docInfo{err: fmt.Errorf("FAQ entry is not accessible: %v", err)}
				mu.Unlock()
				return
			}
			var meta *types.FAQChunkMetadata
			if chunk.ChunkType == types.ChunkTypeFAQ {
				meta, _ = chunk.FAQMetadata()
			}
			mu.Lock()
			results["faq:"+id] = &docInfo{chunk: chunk, faqMeta: meta, chunkCount: 1}
			mu.Unlock()
		}(faqID)
	}

	for _, knowledgeID := range knowledgeIDs {
		wg.Add(1)
		go func(id string) {
			defer wg.Done()

View on GitHub (pinned to 988cbb0330)

Solutions

  1. Verify the FAQ entry exists and is enabled
  2. Confirm its owning knowledge base is within the Agent's search targets
  3. Report per-entry errors to the caller instead of failing the entire request
Defensive patterns

Strategy: try-catch

When it happens

Trigger: Thrown at internal/agent/tools/get_document_info.go:140 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/504632705ac45ab6. Report an issue: GitHub.