List Query Conflicts
Lists every conflict recorded on the chunks a query run retrieved, one entry per conflict.
Entries follow the order of the retrieved chunks, then conflict order within each chunk. An empty data with truncated: false means the run recorded no conflicts.
Conflicts on a chunk that was deleted or is no longer readable are dropped, so this view under-reports once List Query Chunks shows that chunk as unavailable. That view reports conflictCount 0 for such a chunk, so it cannot recover the dropped total either.
A conflict whose other chunk (withNodeId) is unavailable stays in this view, with metadata.availability unavailable and metadata.unavailableReason evidence-unavailable.
For how to read a run’s chunks, conflicts, and missing chunks together, see Investigate an Answer.
Authorization
Path parameters
…/knowledge-fs/spaces/<knowledge base ID>), and the segment after /datasets/new/ in the address bar.Query parameters
next_cursor. Entries are addressed by offset, so 0 starts from the first entry.Length: 1–1000
Responses
One page of conflict entries:
nameisconflict-<n>.metadata.nodeIdis the chunk that holds the conflict.target_idis the chunk it conflicts with, or the same node ID when none is recorded.resource_typeisnode.
null in these views.null on the last page. Send it back as cursor./queries/<query_record_id>/evidence. Informational. This API does not serve it.null in these views.true when more entries exist beyond this page. Follow next_cursor to read them.