List Missing Chunks
Lists the chunks a query run expected but could not use, one entry per chunk. An empty data with truncated: false means the run recorded none.
The entries carry the reason and the entry’s metadata, not the missing text. To read the text, use Get Query Record and inspect steps[].metadata.evidenceBundle.missingEvidence.
For how to read a run’s chunks, conflicts, and missing chunks together, see Investigate an Answer.
1 min read
get/knowledge-fs/spaces/{knowledge_base_id}/traces/{query_record_id}/missing
Request example
Response
get/knowledge-fs/spaces/{knowledge_base_id}/traces/{query_record_id}/missing
Authorization
Path parameters
Knowledge base ID: the last segment of the Service API endpoint shown in the knowledge base's API Access dialog (
…/knowledge-fs/spaces/<knowledge base ID>), and the segment after /datasets/new/ in the address bar.Query parameters
Cursor from the previous page's
next_cursor. Entries are addressed by offset, so 0 starts from the first entry.Length: 1–1000
Responses
application/json
One page of missing-chunk entries:
nameismissing-<n>.target_idis the expected chunk ID when recorded, else the entry name.resource_typeisevidence.
Always
null in these views.Cursor for the next page, or
null on the last page. Send it back as cursor.Internal path of the view, for example
/queries/<query_record_id>/evidence. Informational. This API does not serve it.Always
null in these views.true when more entries exist beyond this page. Follow next_cursor to read them.