What the data for this category looks like
Data related to power grid enterprise business processing mainly comes from internal documents such as official business procedures, expansion application manuals, power outage repair rules, and electricity price policy documents. Updates are triggered temporarily along with policy adjustments and process iterations, with regular quarterly updates of existing documents. The document structure is grouped around major business categories. Each group contains content such as processing steps, required materials, processing time limits, and consultation channels. Fields include business number, service window, contact number, and more. Common units are working days, yuan per kilowatt-hour, household, and others.
What constraints these characteristics impose on the knowledge base retrieval and recall link
The grouping structure by major business categories requires retrieval to be limited to the corresponding folder scope, to avoid retrieving irrelevant content across businesses. Fields include precise business identifiers that can be used to filter recall results. Documents have strong timeliness, so the latest version of process documents must be recalled first. Individual documents are lengthy, so chunking parameters must be set reasonably to ensure the completeness and readability of recalled content. At the same time, most user queries target specific business scenarios, so precise term matching is required to avoid ineffective results from generalized retrieval.
How to set the configuration
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Value | Basis for This Setting |
|---|---|---|
similarity | 0.72–0.80 | Match the precision of power grid business terms, to avoid recalling irrelevant electricity price policies or general service documents |
limit | Top 8 entries | Power grid business documents are concentrated in single business entries; too many results will exceed the context length limit and affect question-and-answer coherence |
searchMode | vector | Prioritize semantic matching of business processes, combined with keyword retrieval to supplement precise business keywords |
usingReRank | Enabled | Rearrange recalled results by business relevance, to prioritize displaying process documents that best match user queries |
datasetSearchUsingExtensionQuery | Enabled | Supplement business-related synonyms, such as matching "application installation" to "new electricity connection" to cover diverse user query expressions |
collectionIds | Specified by business folder ID | Limit retrieval scope to the knowledge base collection for power grid business processing, to avoid mixing non-business documents from other categories |
Three common mistakes
- Failed to call API to upload documents, or no response when uploading Markdown documents via the page. Cause: The
collectionIdsparameter is not specified, or the document contains unescaped special characters, causing the parsing process to interrupt. - Prompted with parsing error when importing a Yuque public link. Cause: The public access permission of the Yuque link is not enabled, or the link does not point to a directly crawlable document page, so it cannot be used as a knowledge base data source.
- Triggered a 60000ms timeout when deleting a folder containing a large number of business documents. Cause: Power grid business documents have a large number and deep hierarchy; batch deletion without configuring batch processing exceeds the default timeout threshold.
How to confirm the configuration is correctly set
- Submit a business-related query, such as "residential new electricity meter installation process", check that the recalled results only include power grid business processing documents with no irrelevant content.
- Upload a test power grid business document or import a compliant public link, check that the upload status shows success with no error prompts.
- Trigger a batch delete operation for a test folder, confirm that the operation completes within 60 seconds with no timeout error triggered.
- View the image links in the question-and-answer results, manually access them to confirm normal loading.
The values provided are common starting points and should be measured 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-09-28.