What this category of data looks like
Reference only; verify against the target FastGPT release and deployment documentation.
What constraints do these characteristics impose on the source citation and traceability link
Data sources for this category are scattered, and update schedules vary significantly. This requires the traceability link to accurately distinguish between historical ticket replies and policy document source types, to avoid confusion of authority levels. Real-time sync configuration must adapt to the timeliness requirements of different sources, to ensure that traceability points to the latest version of content. The matching intent tags in the document structure require the traceability link to associate source entries corresponding to the relevant intent, to ensure that the reply and source matching logic strictly corresponds. The length range of a single reply text requires the traceability link to control the displayed content length, to avoid information overload.
How to Set Configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Adapt to the length range of single reply texts, to avoid context window overflow |
responseData | Enabled | Extract complete metadata of source fields, to support traceability verification |
detail | Full | Retain all fields of source documents, including update time and source path |
| Single recall limit | Top 5 entries | Control the number of displayed sources, to avoid interfering with agent judgment |
| Timeout threshold | 60 seconds | Adapt to response timeliness requirements in hotline scenarios |
| Source sorting rule | Sort by authority | Prioritize displaying authoritative sources such as policy documents |
Three Common Mistakes
- Context citations fail to render Markdown formatting. Cause:
detailis not set to Full, only plain text fragments are returned, and formatting markers are lost. - Some questions cannot be associated with knowledge base files. Cause: The
responseDataconfiguration is not enabled, and the system only calls internal historical ticket replies without associating official knowledge base entries. - Context citations are accidentally removed. Cause: The
responseDataconfiguration is incorrectly disabled, causing all source identifiers to be hidden.
How to Confirm the Configuration Is Complete
- Submit a hotline-related query, check whether source identifiers and update times are displayed below the reply.
- Enter the configuration page, confirm that the
responseDataswitch is in the enabled state, and complete source metadata can be extracted from the logs. - Adjust the
quoteMaxTokenconfiguration, submit a long-text reply query, and check that the reply is not truncated. - View the source sorting rule, confirm that the configuration has taken effect, and authoritative sources are displayed first.
Note: The values listed above are common starting points, and should be evaluated against the reader's own samples.
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.