What Data for This Category Looks Like
Energy metal market data originates from public sources of professional commodity exchanges and industry associations. It covers common segmented varieties including lithium, cobalt, and nickel. Update frequency differs between spot and futures data:
- Spot data updates on a fixed daily trading cycle
- Futures data is pushed in real time during trading sessions and compiled after market close
Documents mostly use structured table formats, with core fields such as product identifier, daily benchmark price, total trading volume, and position size. Some segmented varieties include parameters related to origin premiums. Common price units are yuan/ton or USD/ton.
Constraints for Forms and Interactions
Because data sources are scattered and update frequencies vary, forms must support multi-data source configuration and switching. The interactive interface must provide variety filtering options grouped by data source. With numerous structured fields and segmented parameters, forms must support custom field mapping and dynamic loading of field groups. Scheduled pull tasks must align with the update cycles of different categories. The interactive interface must offer preset update time templates for quick selection. Data validation must cover cross-source field consistency. When fields returned by different data sources do not match, clear prompts must appear in the interactive interface.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
Scheduled Task Trigger Time | "15:30, 16:30, 21:00 on trading days" | Matches typical update timestamps after domestic spot market close and futures night session close, adapting to energy metal data release rhythms |
field_mapping_rules | Automatically map per preset rules for each data source, with manual adjustment support | Field naming varies across data sources, enabling flexible alignment with form display requirements |
max_response_wait_time | 300 seconds | Multi-data source pulling requires waiting for compiled results to prevent task interruption from timeout |
form_field_limit | Top 10 high-frequency fields | Core display fields for energy metals are concentrated; excess fields raise interaction complexity |
data_source_switch_enabled | Enabled | Market data from different sources has minor differences, supporting user-driven view switching |
The parameter values provided on this page are general recommendations used as starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require case-by-case analysis, and it is recommended to test against samples relevant to the specific deployment before finalizing settings.
Three Common Misconfigurations
- Symptom: Execution results from preceding workflow nodes cannot be automatically imported into subsequent AI conversation modules, and the interface displays empty input fields. Cause: The
output_variable_mappingparameter is not configured, and the output of preceding nodes is not bound to the input variables of subsequent modules. - Symptom: When passing TXT format files via an HTTP request node, the backend returns a 400 error code and cannot receive file content. Cause:
request_content_typeis not correctly set tomultipart/form-data, and the file field is not bound to the request parameters. - Symptom: The search reference limit set in the form does not take effect, and the number of returned results exceeds the configured value. Cause:
search_result_limitis only set in the knowledge base configuration, and this parameter is not synchronously bound to the form's display logic.
How to Verify Successful Configuration
- Manually trigger the configured scheduled pull task, and verify that the data timestamp loaded by the form matches the latest update time marked by the data source.
- Select different sources from the form's data source switching menu, and confirm that the displayed field groups match the public structure of the corresponding data source.
- Modify the
field_mapping_rulesparameter and submit it, then check that the form correctly displays the adjusted field names and order. - Simulate a timeout scenario for multi-data source pulling, and confirm that the interface displays the expected timeout prompt message.
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.