What the data for this category looks like
Minor metal research report data primarily comes from monthly statistics released by the Minor Metal Branch of the China Nonferrous Metals Industry Association, securities firm nonferrous metal industry research reports, and professional spot information platforms. There are three update schedules:
- Spot price and inventory data is updated daily
- Industry supply and demand statistics are released weekly or monthly
- Securities firm research reports are updated in real time alongside policy changes and supply and demand inflection points
Individual research report documents include core supply and demand logic, quantitative indicators, cost calculations, and downstream application analysis. Fields include variety name, trading market, price unit (yuan/ton), inventory unit (ton), and other standard fields. Some overseas research reports include converted data denominated in US dollars.
What constraints do these characteristics impose on workflow orchestration?
The multi-source nature, varied update schedules, and differentiated formats of minor metal research reports create multiple constraints for workflow orchestration:
- Daily updated spot price and inventory data require scheduled trigger nodes in the workflow to avoid calling outdated data.
- Unit differences across data sources, such as domestic use of yuan/ton and overseas use of US dollars/ton, require data standardization nodes in the workflow to unify field formats.
- Individual in-depth research reports may exceed 10,000 words, requiring segmented recall thresholds to avoid exceeding the model context window.
- Coverage of subdivided varieties including lithium, cobalt, rare earths and others requires the workflow to support filtering recall results by variety tags to reduce irrelevant data interference.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
Scheduled Trigger Cycle | Trigger once at 00:00 and once at 12:00 daily | Matches the daily update cadence of minor metal spot data, covers morning and evening market changes |
Recall Count | Top 8 entries | Balances research report information richness and model context window usage, avoids overload in single-round calls |
Similarity Threshold | 0.75–0.85 | Filters low-relevance research report content, focuses on core supply and demand logic for minor metal varieties |
maxContext | 8000–12000 characters | Adapts to the length of most segmented minor metal research reports, avoids exceeding context limits of basic large models |
Data Standardization Switch | Enabled | Unifies price and inventory units across different data sources, eliminates recognition errors caused by format differences |
PARSE_FILE_TIMEOUT_SECONDS | 600 seconds | Adapts to long document parsing time, avoids parsing timeout failures for in-depth research reports |
The parameter values provided on this page are common recommended starting points for determining configurations. Actual values are affected by material form, data volume, and business rules. Specific issues require case-by-case analysis, and it is recommended to conduct tests on your own samples before finalizing settings.
Three Common Misconfigurations
- Phenomenon: Workflow returns results with a delay of more than 10 seconds, or an
ETIMEDOUTerror occurs. Cause: ThePARSE_FILE_TIMEOUT_SECONDSparameter is not set reasonably, and long document parsing times out without triggering a retry mechanism. - Phenomenon: An error
Key is error. You need to use the app key rather than the account keyis returned when calling the workflow. Cause: An account key is used when calling the interface, an application key is not used, and the workflow's calling credentials are not configured correctly. - Phenomenon: Only two preset items are displayed in the global variables available for selection in the workflow editing interface. Cause: The 4.9.10 version of the interface is used, and the configuration entry for global variables was adjusted in this version. Custom variables must be added by entering the "Application Settings - Global Variables" page.
How to Confirm Correct Configuration
- Trigger the workflow once, check whether the research report varieties in the returned results match the preset minor metal tags, and confirm that the filtering logic is effective.
- Check the workflow's scheduled trigger logs to confirm that it runs automatically according to the set cycle, with no missed trigger records.
- Call the workflow interface with the correct application key, and verify that no key error prompts appear.
- View the parsed research report data fields, confirm that units such as price and inventory have been unified to the preset format, with no format confusion.
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.