What the data for this category looks like
Data for this category comes from the national public resource trading platform, natural resource trading systems, property right exchange systems, and state-owned asset supervision systems. The update frequency is daily. Commonly used documents include transfer announcements, trading guidelines, bid application materials, margin vouchers, transaction confirmation letters, listing result announcements, and property right transfer specifications. Typical data fields include transaction subject ownership number, type, starting price, margin amount, bidding rules, and more. Units include yuan, parcel, item, and others. Different documents have different required core field specifications.
What constraints these characteristics impose on the "workflow orchestration" link
Multiple system data sources require the workflow to configure variables mapping rules to enable unified reading of data across different systems. The daily update frequency requires the workflow to set a scheduled synchronization node to ensure the latest transaction data is used for consulting replies. Diverse document types require splitting into separate processing branches such as ownership review, bidding confirmation, and transaction announcement, with accurate branching achieved by matching execution results to nodeId. Fields involve core information such as ownership and funds, so a verification step must be added to prevent erroneous data from entering the reply process. Retry and failure branches must also be configured to handle occasional system anomalies.
How to set the configurations
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
| Variable mapping rules | Bind business document fields one-to-one with variables key names | Ensure the workflow can accurately read core data such as transaction subject ownership and margin |
| Node timeout period | 600 seconds | Matches the average processing duration of the ownership verification link |
| Context window length | 8000–12000 characters | Accommodates the full content of multiple transaction documents |
| Branch trigger condition | Match node execution results with nodeId | Accurately branch to different business links such as ownership review and bidding confirmation |
| Retry count | 3 times | Addresses scenarios of occasional failures in system calls |
| Knowledge base recall count | Top 5 entries | Controls the precision of returned information, avoiding interference from redundant content in replies |
Reference only; verify against the target FastGPT release and deployment documentation.
Three common mistakes
- After the workflow executes a designated reply node, no HTML content is displayed on the interface and the workflow jumps directly to the next branch node. The cause is that the output type of this node is not configured as rich text, resulting in HTML tags being automatically filtered by the system.
- The overall runtime of the workflow exceeds expectations. The cause is that the number of single knowledge base recalls is not limited, and the context reuse mechanism is not enabled, resulting in repeated calls to system resources.
- The answer after tool call includes the input and response reference fields of the knowledge base search. The cause is that the configuration for automatically appending original retrieval logs in the workflow is not turned off. Only the results generated by the tool should be retained.
How to confirm the configuration is correct
- Manually trigger the workflow, enter the transfer announcement number of a land parcel, and check whether the corresponding ownership information and transaction conditions are correctly pulled into
variables. - Simulate a node timeout scenario, check whether the preset retry mechanism and failure branch are triggered, and whether the process jumps normally.
- Call the tool to generate a transaction consulting reply, and check whether the returned content only includes the results generated by the tool, with no additional search log references.
- Adjust the branch trigger condition, and verify whether different node results are correctly branched to the corresponding business processing links.
The values listed here are common starting points, and should be evaluated against your own specific samples and use cases.
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.