What the documents look like
Receiving and putaway handles the first physical-versus-record confirmation when goods enter the warehouse. The working data comes from the WMS, ERP purchasing, supplier delivery notes and barcode scanning. When this step goes wrong, the visible consequences are inventory that does not match physical stock, later picking errors and disputes with suppliers. The daily documents are the purchase arrival note, the receiving inspection sheet, the putaway task and the discrepancy report.
For an upgrade, the constraint is that the same arrival note, inspection sheet and putaway task must be interpretable under one permission model before and after the change. The authorization state at handover cannot be replaced by a retrieval result or by a form entry. A record that can be found is not the same as a person being authorized to act on it.
The upgrade notes for this version list two manually triggered scripts: 20261008_migrate_chunk_training and 20261009_migrate_dataset_rebuild_status. Neither blocks service startup, and the second depends on the first being complete. Before either is run, the operator must confirm that all old-version FastGPT App and Pro instances have fully stopped and that old task leases have expired.
A hypothetical drill sample: a warehouse WMS administrator prepares handover material before an upgrade. Purchase arrival note text: "Arrival note DH-2026-0417, supplier A, purchase order CG-3312, arrival quantity 480 pieces, status is pending inspection." Receiving inspection sheet text: "Inspection sheet YS-2026-0417, corresponding arrival note DH-2026-0417, received 480 pieces, inspector: Li, status: inspected, pending putaway." Putaway task text: "Task SJ-2026-0417, linked inspection sheet YS-2026-0417, target bin B-12, assignee: unassigned, status is pending assignment." Draft sentence to be judged: "Putaway task SJ-2026-0417 has been completed by Li, and inventory has been synchronized." The comparison points against the source are the assignee and the status: the source assignee is unassigned and the status is pending assignment, the inspector Li is a different field from the putaway assignee, and inventory synchronization has no record in the source.
Constraints at the upgrades step
The two migration scripts are manual triggers that do not block startup. Running a script, adjusting member permissions and handing over a putaway task are separate actions. The completion state of one action cannot be inferred from another. A script that has an entry point for triggering is not a script that has run. A migration that depends on another migration is not complete because the first one was triggered.
Permission and handover management at this stage also has to keep the same authorization reading on both sides of the upgrade. If a member's access to arrival notes, inspection sheets or putaway tasks is changed during the upgrade window, the change belongs to the permission action, not to the migration action, and the two records must be kept apart. Retrieval of a document does not grant the right to act on it, and a form that collects a value does not perform business verification, approval, a database write or external synchronization. Those steps require their own downstream implementation, and the document set here does not define one.
The upgrade notes also state that the scripts should be run only after old instances are fully stopped and old leases have expired. Whether those conditions hold is a manual check against instance state and lease records, not a value that a retrieval or a form can supply.
Configuration and implementation checks
The table below lists documented settings or implementation checks relevant to this page. Where a value appears, it is a hypothetical starting point for this drill, not an official default.
| Item | Hypothetical starting point for this drill | Reason and comparison method |
|---|---|---|
AIPROXY_API_ENDPOINT | Assume http://aiproxy:3000 | The document requires the AI Proxy root address without /v1; compare the configured string character by character against that format |
AIPROXY_API_TOKEN | Assume a non-empty string | The document requires a non-empty administrator token consistent with the server side; compare against the AI Proxy server configuration value |
FILE_TOKEN_KEY, AES256_SECRET_KEY, INVOKE_TOKEN_SECRET | Assume random strong keys for each | The document marks these as required at runtime; check the stated length minimums and whether an example value was reused |
PRO_URL and PRO_TOKEN | Assume both configured together | The document states PRO_TOKEN is required when PRO_URL is set on App; check whether both are present at the same time |
DEFAULT_TEAM_BASIC_PERMISSIONS_ENABLED | Assume the same value on App and Pro Admin | The document requires the two services to stay consistent; compare the two configured values |
| Upgrade script preconditions | Manual check item | The document requires confirming old instances are stopped and old leases expired before execution; compare against instance state and lease records |
Three common errors
- Treating the inspection sheet status "inspected, pending putaway" as evidence that the putaway task is complete. The input is the inspection sheet and the putaway task; the comparison object is the assignee and status fields of the putaway task; the inspection sheet status and the putaway task status are different fields of different documents and cannot stand in for each other.
- Treating a retrieved arrival note, inspection sheet or putaway task record as an obtained operating authorization. The input is the retrieval result or a filled form value; the comparison object is the authorization record itself; retrieval and collected form values do not constitute a permission grant or a completed handover.
- Treating the upgrade script attribute "manually triggered, does not block startup" as evidence that the script has run or the migration has completed. The input is the script identifier and trigger method from the upgrade notes; the comparison object is the actual execution record; a pending trigger state does not show execution and does not show a migration result.
How to verify the setup
- Input the three source texts and the draft sentence from the hypothetical sample, and compare the assignee and status stated in the draft sentence against the corresponding source fields. If the draft sentence says Li completed the putaway while the task source shows assignee unassigned and status pending assignment, the sentence is unsupported and the evidence gap must be recorded.
- Input the hypothetical
AIPROXY_API_ENDPOINTandAIPROXY_API_TOKENvalues, and compare whether the address contains/v1and whether the token is non-empty. If the address appends a path or the token is empty, the values do not match the documented requirement, and startup validation is expected to fail. - Input the upgrade script identifiers together with the records of instance stop state and lease state, and compare whether an actual execution record exists. If only a trigger entry is present and no execution record exists, the migration completion state remains unverified and is not judged complete.