Understand knowledge processing status
Interpret pending, processing, ready, error, and cancellation states for a knowledge source.
2 min read
- Project
- Knowledge
The Knowledge source list is where Chat4U reports waiting, processing, ready, or failed source states.
Read status as indexing progress—not as a promise about answer quality.
- Finish with
- The correct next action for each source status
Each knowledge source has a status representing its indexing lifecycle.
| Status | Meaning | What to do |
|---|---|---|
| Pending | The source is queued, or a seeded website configuration is waiting for an explicit start. | Start an awaiting website source, or allow a queued job to begin. |
| Processing | Chat4U is scraping, transforming, or indexing the source. | Wait; do not start a duplicate run. You can request cancellation if necessary. |
| Ready | The latest successful content is available for retrieval. | Review the scope, assignment, and sample answers. |
| Error | The run did not complete. The source stores an error message. | Read the message, correct the cause, then re-sync. |
For URL sources, progress can identify phases such as queued, scraping, applying a budget cap, taxonomy and page transformation, indexing, and finalizing. Progress is operational visibility; page counts can change as the crawl discovers pages, applies scope, or discards unsuitable content.
Awaiting start is different from waiting in a queue
A pending website source created from project setup can be intentionally awaiting start. The dashboard labels it as a pending scrape and offers Start Scraping. This lets an operator review URL, mode, limits, and attestation before the first crawl.
By contrast, a normal pending source has already been queued for work. If it remains pending longer than expected, inspect the source details and its run history before trying another action.
Cancel, then recover carefully
Cancellation is a request. A pending run can stop immediately; an in-progress run is signaled to stop and may take time to settle. A canceled source is surfaced as an error status with a cancellation phase, so the dashboard can distinguish it from another failure. Re-sync only after the prior job is no longer active.
Last updated on