What data for this category looks like
Securities financial report data primarily comes from official disclosure platforms of the Shanghai, Shenzhen, Beijing Stock Exchanges and the Hong Kong Stock Exchange. Annual reports must be disclosed within four months after the end of the accounting year. Quarterly reports must be disclosed within one month after the end of the quarter. Temporary reports such as performance forecasts and related transaction announcements are updated in real time.
Document structure includes fixed sections: main financial statements, management's discussion and analysis, related transaction explanations, and more. Fields include earnings per share, attributable net profit, return on net assets, and others. Units include yuan, percentage, multiple, and more. A complete annual report PDF typically ranges from tens to hundreds of megabytes in size.
What constraints do these characteristics impose on the knowledge base retrieval and recall link?
The long document structure and high-frequency update requirements of securities financial reports mean the retrieval and recall link must support large file chunk parsing and incremental synchronization. This prevents parsing failures or incomplete recall caused by overly large single files.
The dense professional terminology in fields requires precise semantic matching during recall, so a high similarity threshold must be set. The fixed chapter structure and field system require recall results to be categorized by financial report chapters, to avoid irrelevant content mixing into retrieval results.
The real-time update requirement for temporary reports requires shortening the synchronization cycle to ensure the timeliness of knowledge base data.
How to set the configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
maxSegmentSize | 800–1200 characters | Securities financial reports contain dense professional terminology and complete indicator descriptions. This segment length preserves context integrity and avoids truncating key financial data |
recallTopK | Top 10–15 results | Financial report analysis requires covering multi-dimensional indicators. A sufficient candidate set can match precise needs across different query scenarios |
similarityThreshold | 0.75–0.85 | Financial report terminology is highly professional. A high similarity threshold filters generalized irrelevant matches and ensures the accuracy of recall results |
PARSE_FILE_TIMEOUT_SECONDS | 600 seconds | Parsing a complete annual report takes a long time. This timeout prevents interruptions during large file parsing |
autoSyncInterval | Daily incremental sync | Adapts to the update frequency of quarterly reports and temporary reports, ensuring the timeliness of knowledge base data |
UPLOAD_FILE_MAX_SIZE | 500 MB | Matches the typical size of a complete annual report PDF, preventing upload failures |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material format, data volume, and business rules. Specific issues require individual analysis. It is recommended to test on your own samples before finalizing settings.
Three common mistakes
- Phenomenon: In FastGPT v4.9.0 and later versions, workflow runtime generates gpt-4o-mini call error logs, but the model call is not actively configured in the workflow. Cause: The knowledge base automatic question-answer pair extraction link uses the globally configured generation model by default. If this link is not disabled, it will trigger model calls, which confuses with the business workflow's call chain.
- Phenomenon: After uploading financial report documents, the internal directory structure is automatically deleted, and duplicate content is also cleaned up. Cause: The automatic directory cleaning configuration during document parsing is not turned off. The default rules remove duplicate directory markers and hierarchical structures within documents.
- Phenomenon: The knowledge base question-answer pair extraction task gets stuck in training, and no corresponding request is generated in the call log. Cause: Insufficient computing resource quotas are configured, or the task queue is backlogged and does not trigger scheduling, and a reasonable task timeout period is not set.
How to confirm the configuration is correct
- Upload a complete annual report PDF, check if the parsed text chunks retain complete financial indicator descriptions, and verify that the chunk length matches the preset configuration.
- Initiate a query containing specific financial report terminology, check if the number of recall results and similarity match the preset rules, and confirm that the latest updated financial report data is recalled first.
- Manually trigger a question-answer pair extraction task, check if the task completes within the preset time, and confirm that the corresponding request is generated in the call log.
- Perform a knowledge base export operation, check if a download link is normally generated, and confirm that the storage path and permission configuration take effect.
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-14.