What data looks like for this category
Coal-power integration documents and supporting data include monthly production ledgers for coal mining, daily power dispatch reports, safety inspection records, coal purchase and sales contracts, power grid connection approval documents, project feasibility study reports, annual settlement reports, and more. Data update rhythms are as follows: dispatch logs are updated daily, contracts and approval documents are updated as business nodes are completed, and annual reports are updated per fiscal year. Document structures typically include fields such as mine number, coal type, power generation, settlement amount, and approval nodes. Units include megawatt-hours, tons, yuan per ton, and others.
Constraints Imposed on Source Citation and Traceability
Coal-power integration documents involve cross-departmental data across multiple stages. A single document may be linked to dozens of supporting files, which requires high precision for traceability. The multi-field document structure requires matching specific business fields during traceability to avoid generalized associations. Frequently updated dispatch logs and contract documents require the knowledge base sync frequency to match business rhythms. Otherwise, cited content will not match the latest business data. The existence of long documents also requires retaining complete chapter and page information of the original content during traceability, so that business personnel can quickly locate the supporting basis.
How to Configure Settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Maximum Citation Token Count | 8000–12000 token | Most coal-power integration documents range from thousands to tens of thousands of characters in length, requiring full coverage of cited supporting content |
| Source Data Return Toggle | Enabled | Need to link to specific coal-power industry business fields such as original document approval nodes and generation time, to ensure complete traceability information |
| Detail Display Mode | Show only associated content | Avoid redundant information interfering with business personnel viewing core document content, and focus on traceability basis |
| Knowledge Base Sync Cycle | Sync at 2:00 AM daily | Match the daily update rhythm of dispatch logs, ensuring the latest business data can be associated in a timely manner |
| Source Data Recall Limit | Top 6 entries | Cover multiple supporting files linked to a single document, such as a single purchase contract and multiple daily dispatch sheets |
Three Common Misconfigurations
- Phenomenon: Some workflow nodes cannot hide cited source content, and only global visibility configuration is available. Reason: The source data display permission is not separately set in the corresponding workflow node, and the global switch is mistakenly used as the only configuration item.
- Phenomenon: Only source data links are returned after calling, and no corresponding document drafting content is generated. Reason: Only the source data recall logic is configured, and the answer generation link is not enabled, resulting in only the original documents being returned without completing the integration of business documents.
- Phenomenon: Cited content is truncated or key fields are missing. Reason:
quoteMaxTokenis set too small, failing to cover complete supporting document content, or knowledge base chunking does not retain coal-power industry-specific fields such as mine number and power generation, leading to insufficient traceability matching accuracy.
How to Verify Proper Configuration
- Upload a coal purchase and sales contract document, initiate a drafting request, and check whether the returned result is linked to exclusive fields such as the contract's approval record and signing date.
- Adjust the
quoteMaxTokenparameter to a reasonable range, upload a dispatch report exceeding 10,000 characters, and check whether the cited content is fully displayed without truncation. - Configure two parallel nodes in the workflow, enable and disable source data display respectively, and verify whether the visibility configuration between nodes takes effect.
- Wait for the daily sync cycle to end, upload a newly added dispatch log, initiate an associated drafting request, and check whether the new data is correctly linked to the generated document.
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.