What this category of data looks like
Data for this category comes from slab or billet batches, heating furnaces, mill automatic control systems, online thickness and width measuring equipment, surface inspection devices, and MES systems. Data is generated in real time per coil or individual steel piece. Daily associated documents include rolling plans, heating schedules, rolling regulations, plate shape and thickness records, surface quality reports, and quality certificates. Core fields include batch identifiers, heating temperature, rolling reduction, thickness deviation, surface defect type and corresponding location. Units include degrees Celsius, millimeters, meters, and others.
What constraints these characteristics impose on the "workflow orchestration" link
This category of data has strong real-time performance and is generated per coil or individual steel piece. Workflows must be bound to batch identifiers as the core associated parameter to avoid mixing data from different steel coils. Multi-source heterogeneous data sources require workflow nodes to support cross-system data pulling and association. Core parameters passed between nodes must be configured via variables. Diverse daily document types require workflows to adapt to reading data sources in different formats, such as rolling plans and quality reports. Errors directly affect product grades and equipment safety. Workflows must set exception branches and failure handling mechanisms to trigger alerts or rollbacks when processes interrupt.
How to set the configurations
These configurations are based on FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Trigger Mode | Triggered by steel coil batch number | Data is generated per coil or individual piece; a unique batch identifier is required to start the workflow |
variables Variable Binding | Bind batch number, heating temperature threshold, surface defect judgment threshold | Used to pass core business parameters across nodes, and associate multi-source data from MES, online inspection systems, and other sources |
nodeId Node Binding | Assign a unique nodeId to each data pulling node | Avoid confusion in node execution order, and ensure data flows according to batches |
| Tool Call Timeout | 600 seconds | Online inspection data is generated in real time; sufficient time must be reserved for pulling and analyzing data |
| Node Failure Retry Count | 3 times | Address temporary disconnections from mill automatic control systems |
| Original File Preview Association | Associate imported original quality certificates and rolling records in the knowledge base | Enable online viewing of original document fragments corresponding to content |
Three common mistakes
- Phenomenon: Generated share links point to
http://localhost:3000/chat/and cannot be accessed externally. Cause: The custom domain for workflow publishing was not configured, and the default local deployment address was used instead. - Phenomenon: The process stalls after executing a tool call node, with no return results. Cause: Database connection parameter binding was not configured correctly, or the tool call timeout period was not set, so no exception branch was triggered after connection timeout.
- Phenomenon: Original document details for corresponding fragments cannot be viewed in conversations. Cause: Original data sources such as quality certificates and rolling records imported into the knowledge base were not associated; only sliced text fragments were imported.
How to confirm the configuration is complete
- Trigger test: Upload batch data for a single steel coil, verify that the workflow starts automatically and no cross-batch data is mixed in.
- Timeout and retry test: Simulate a tool call timeout scenario, verify that the workflow triggers retries or exception branches.
- Original file preview test: Click a quality report fragment in the conversation interface, confirm that it jumps to the imported original document details.
- Published link test: Generate a share link, verify that the conversation interface can be accessed via an external network, and no local address error occurs.
Note: The configuration values listed above are common starting points. Adjust them based on your own specific samples and operational requirements.