What the documents look like
A fresh-food concession counter in a hypermarket is run on site by a supplier, and revenue is shared according to sales. The store fresh-food department, the concession supplier and the store manager all take part in daily operations. This structure determines which materials matter at the deployment and upgrade step: the concession contract, the daily sales report, the loss report and the food purchase inspection record. These materials are produced daily or per batch, and their current state has to be confirmed item by item at handover. The daily sales report and the loss report relate to weighed-sales reconciliation and loss sharing, while the inspection record relates to voucher checks. Together they form the basis for checking operational authority at handover. Retrieval results or submitted forms do not by themselves constitute authorized execution, and a pending review state does not demonstrate that an operation is unavailable.
Hypothetical drill sample: an excerpt from a concession contract signed by a store fresh-food department and a concession supplier reads, "Party A is the fresh-food department of a certain hypermarket; Party B is a certain concession supplier; the contract term runs from 1 January 2026 to 31 December 2026; Party B operates the fresh-food counter on site and shares revenue on monthly sales." A daily sales report for the same day records, "15 March 2026, counter sales amount RMB 8,000, loss amount RMB 200." A food purchase inspection record reads, "15 March 2026, incoming batch A, supplier a certain party, inspector a certain person, status inspected." The draft sentence to be assessed is, "The concession supplier has confirmed the loss sharing for 15 March 2026, and handover is complete." The loss-sharing confirmation record required by that sentence does not appear in the materials above, so the sentence is unsupported.
Constraints at the upgrades step
After a version upgrade, old configuration names cannot be used to infer current behaviour. Operational authority and handover management require checking the current version, the target version and the corresponding upgrade notes first, then carrying out dependency and backup checks. The upgrade notes for this version describe two manual migration scripts: the historical chunk training task migration and the dataset rebuild status migration. Both are described as manual, non-blocking to service startup, and the second depends on the first having completed. The notes state that the migration should be clicked only after all old-version FastGPT App and Pro instances in the cluster have fully stopped and old task leases have expired. Whether a given environment has actually reached that state is a matter for its own operators to confirm; the page does not assert that any cluster has done so.
Configuration names from an earlier release cannot stand in for current required settings. From V4.17.0, AI Proxy is a required dependency, and both the App and the Admin service that reuses App/Service configuration must set a root address and a non-empty administrator token. Missing either one causes startup validation to fail. Legacy single-model addresses do not replace these two settings. At the same time, a form that collects values, a retrieval hit, or a pending state does not grant authority to execute a handover action; those remain downstream implementation matters.
Configuration and implementation checks
The table below covers settings and verification items that the official documents describe and that bear on this page's materials and main task. Values marked as a hypothetical starting point are chosen for this drill only; they are not official defaults and were not tested.
| Configuration item | Hypothetical starting point for this drill | Reason and comparison method |
|---|---|---|
AIPROXY_API_ENDPOINT | http://aiproxy:3000 | Documented as the AI Proxy root address without /v1; compare against any legacy single-model address to confirm the old value is not in use |
AIPROXY_API_TOKEN | Placeholder value | Documented as required non-empty and consistent with the server side; compare against the AI Proxy server configuration |
FILE_TOKEN_KEY | Random strong key | Required at runtime, at least 6 characters; compare against sample values to confirm no sample value is reused |
AES256_SECRET_KEY | Random strong key | Required at runtime, at least 6 characters; compare against sample values |
INVOKE_TOKEN_SECRET | Random strong key | Required at runtime, at least 32 characters; compare against sample values |
| Upgrade script check | Manual trigger, non-blocking to startup | Documented as requiring all old instances stopped and old task leases expired before execution; compare the execution time against the stopped state |
Three common errors
- Treating a retrieval result or a form submission as authorized execution. In the sample, the draft sentence claims loss sharing has been confirmed, while no loss-sharing confirmation record appears in the materials; the sentence is unsupported.
- Inferring current behaviour from an old configuration name. After the upgrade,
AIPROXY_API_ENDPOINTandAIPROXY_API_TOKENare required dependencies, and a legacy single-model address does not substitute for them. - Mixing evidence from different fields. In the sample, the contract term, the sales amount and the inspection status belong to different materials and cannot be used to derive a loss-sharing confirmation.
How to verify the setup
- Input the sample contract text and the draft sentence, then compare whether the loss-sharing confirmation record required by the draft sentence appears in the materials. The materials do not state that record, so the result is unsupported.
- Input the post-upgrade environment variable configuration, then compare whether
AIPROXY_API_ENDPOINTis a root address without/v1appended and whetherAIPROXY_API_TOKENis non-empty. If either condition does not hold, record it as a configuration gap. - Input the upgrade script execution time and the instance stopped state, then compare whether execution occurred after all old instances were fully stopped and old task leases had expired. If that condition is not met, record it as pending verification.