This configuration applies to FastGPT v4.17.0.
What This Category of Data Looks Like
The core data for this category comes from customer-submitted warranty work orders, system operation logs, contract warranty clauses, and project version records. Daily processing documents include standardized warranty work orders, defect confirmation sheets, repair operation records, and customer closure confirmation sheets. Data is updated daily or synchronized upon completion of each work order. Documents include structured fields such as defect number and associated version number, plus unstructured on-site descriptions and communication records.
Constraints Imposed on Knowledge Base Retrieval and Recall
Dispersed data sources with both structured and unstructured content require retrieval to balance vector semantic matching and precise keyword matching. This avoids missing responsibility boundary requirements in contract clauses. The high-frequency update feature requires the retrieval link to support real-time or near-real-time data synchronization, to prevent returning outdated repair solutions. Exclusive document types and fields require retrieval to be limited to warranty-related knowledge base collections. This prevents mixing irrelevant data from operation and maintenance or other categories, and adapts to precise matching requirements for specific fields such as defect numbers and version numbers.
How to Configure the Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
similarity | 0.72–0.80 | Warranty defect descriptions require precise matching to avoid introducing unrelated non-warranty documents. This range balances recall coverage and relevance |
limit | Top 8–12 entries | Covers multi-scenario repair records for the same type of defect, while controlling the total number of returned results to stay within context window limits |
usingReRank | Enabled | Sort recalled repair records and work order cases by relevance to help engineers quickly determine responsibility boundaries and repair solutions |
searchMode | Hybrid vector + keyword | Adapts to dual needs: keyword matching for contract warranty clauses and semantic matching for defect descriptions |
datasetSearchUsingExtensionQuery | Enabled | Customer-submitted defect descriptions are often colloquial. Automatically expanding them to standardized technical terms improves recall accuracy |
collectionIds | Bind exclusive collection IDs for warranty work orders and defect confirmation sheets | Limit retrieval scope to only documents for this category, to avoid mixing in knowledge base data from other operation and maintenance or integration categories |
Three Common Configuration Errors
- Retrieval reordering returns false, and no relevance sorting change appears on the interface. Cause: The reordering model is not bound to the corresponding warranty knowledge base collection, or the
usingReRankconfiguration is not correctly enabled. - A large number of non-warranty documents are included in retrieval results, making accurate location of defect-related content impossible. Cause: The
collectionIdsconfiguration to limit the exclusive knowledge base collection is not set, and knowledge base data from other categories is mixed in. - The latest repair records and customer confirmation sheets cannot be recalled. Cause: The knowledge base is not synchronized at the daily or per-order frequency, or real-time data synchronization configuration is not enabled.
How to Confirm Correct Configuration
- Upload one latest warranty work order sample as the retrieval keyword, and check whether returned results only include warranty-related repair records and defect confirmation sheets.
- Manually trigger retrieval and view result sorting. Confirm that results are arranged from highest to lowest relevance, and verify that the
usingReRankfunction is enabled. - Submit a colloquial defect description, and check whether retrieval results match the repair solution for the corresponding version. Verify that the
datasetSearchUsingExtensionQueryfunction is enabled. - Check the update time of retrieval results, confirm that it matches the time of the most recently submitted work order or repair record, and verify that the data synchronization configuration is correct.
The values provided are common starting points and should be evaluated against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.