Reference only; verify against the target FastGPT release and deployment documentation.
What the data for this category looks like
Mining and mineral processing business data primarily originates from production ledgers, mineral processing process parameter records, safety inspection logs, and business approval documents. Data update frequencies cover three categories: real-time (on-site inspection records), daily (production daily reports), and monthly (settlement reports). Document formats include long text logs of 100,000 Chinese characters per file, and structured Excel production data with over 15,000 rows. Fields include raw ore grade, mineral processing recovery rate, equipment operating hours, approval order numbers, and other relevant items. Corresponding units include percentage, hour, ton, and other professional mining terminology units.
Constraints for forms and interactions
Long text inspection logs and large-row Excel data require the form interaction module to support large file upload and chunked parsing, to avoid single-input overflow. Fields with multiple professional units require the form to display corresponding unit prompts for each field, to prevent user input confusion. Business data with different update frequencies requires the form to support selecting data time ranges based on business scenarios, to adapt to different verification logic for real-time ledgers and monthly settlements. On-site inspection image data requirements require the form to support image upload parsing in binary stream and base64 formats.
How to configure the settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
formInput input length limit | 8000–12000 characters | Adapts to the chunked parsing requirements of 100,000 Chinese character documents, avoiding single-input overflow |
userSelect business classification | Three categories: mining / mineral processing / safety approval | Matches the three-level business scenarios of mining and mineral processing, reducing user selection costs |
| Single upload file limit | 1000 MB | Supports batch upload of over 15,000-row Excel and long text documents |
| Field unit prompt | Displayed synchronously with the field | Prevents input confusion for professional units such as raw ore grade and mineral processing recovery rate |
| Interaction timeout threshold | 600 seconds | Adapts to the time requirements of large file parsing and multi-turn conversations |
Three common misconfigurations
- After uploading over 15,000-row Excel production data, the prompt "Incomplete command or request" is returned. The cause is insufficient single upload file limit configuration, leading to data truncation during large file parsing.
- After entering a 100,000 Chinese character inspection log document, the interaction process becomes unresponsive. The cause is failure to adjust the input length limit for
formInput, exceeding the default threshold and causing the request to be blocked. - After uploading on-site inspection images in base64 format, content parsing cannot be triggered. The cause is failure to enable image adaptation configuration in the form interaction module, and failure to associate the corresponding parsing module.
How to verify the configuration is complete
- Upload a single 15,000+ row Excel production data file, check whether it can be fully parsed and proceed to subsequent interaction links.
- Enter a single 100,000 Chinese character inspection log, check whether
formInputallows complete input and submission. - Select a business classification option from
userSelect, check whether the corresponding data verification rules can be correctly matched. - Upload on-site images in base64 format, check whether the corresponding parsing process can be triggered.
The values provided here 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.