What Data Looks Like for This Category
This category covers end-to-end documentation for slaughterhouses and cooked meat, frozen prepared food manufacturers. Included documents are animal quarantine certificates, slaughter and cutting records, ingredient marination logs, thermal processing parameter logs, cold chain temperature logs, microbial test reports, and more. Data sources include animal quarantine information, supplier batch codes, production traceability chains, real-time temperature collection, metal detection results, and laboratory test data. Updates follow production batches and shifts. Cold chain temperature data requires continuous collection and updates. Each single batch of data links information across quarantine, raw materials, processing, and inspection stages.
Constraints for Source Citation and Traceability
Traceability data for this category must be tied to batch and quarantine information. Each individual data entry links multiple stage fields. Accurate batch code matching is required when citing data. Continuously collected cold chain temperature data has a high update frequency. Ensure that the latest time-period logs are called during traceability. Records from raw-cooked zoning and processing links must be strictly isolated. Distinguish raw material and finished product data when citing to avoid confusion of cross-contamination-related records. Data fields include quarantine status related to biological risks. Retain compliance identifiers from original fields when citing to ensure traceability results can be traced back to the source quarantine link.
Configuration Settings
The following configurations are based on FastGPT v4.17.0, and are adapted to traceability requirements for the meat products and slaughter processing category.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Single Recall Limit | Top 6 entries | This category has a moderate amount of data linked per batch. Too many recalls will increase context redundancy, while too few will fail to cover full-stage traceability information |
| Maximum Context | 8000–12000 token | Must accommodate multi-stage data such as quarantine certificates, batch records, and temperature logs. Adjust based on actual measurement calibration |
quoteMaxToken | 1500 token | Matches the average length of a single traceability document, avoiding truncation of critical batch and quarantine information |
| Return Original Data | Enabled | Must retain fields such as original document quarantine numbers and temperature values to meet compliant traceability requirements |
| Detail Toggle | Enabled | Displays specific fields of original documents, making it easier to verify the completeness of traceability information |
Three Common Configuration Errors
- Symptom: The system has no response for an extended period, and the interface displays a loading timeout. Cause: The number of documents recalled in a single session is not limited, resulting in loading too much batch and temperature log data that exceeds the system context capacity limit.
- Symptom: Responses only generate generic statements, and do not cite original quarantine or production records from the knowledge base. Cause: The Return Original Data configuration is not enabled, so the system does not call exclusive document content from the knowledge base.
- Symptom: Batch fields returned by the knowledge base cannot be selected in workflow code nodes. Cause: The Detail Toggle is not enabled in the knowledge base configuration, and the field information of original documents is not exposed, causing the node to fail to recognize available variables.
How to Verify Successful Configuration
- Upload a single batch's quarantine certificate and temperature logs to the associated knowledge base, initiate a traceability query, and verify that the returned results include all fields of the original documents.
- Check the context length returned by the query, confirm that it does not exceed the configured maximum context value, and there are no document truncation prompts.
- Open the variable selection panel of the workflow node, and confirm that batch codes, quarantine numbers, and other fields returned by the knowledge base can be selected.
- Check the system operation logs, confirm that the corresponding documents in the knowledge base are called, and there are no context overflow error messages.
The values provided are common starting points and should be measured against the relevant organization's own sample data.