> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/files-knowledge-and-retrieval/indexing-status-and-search-readiness.md).

# Indexing Status and Search Readiness

A file becomes searchable only after the required processing completes. Check the target resource’s status instead of relying only on the upload response or aggregate counts.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FmAI88Kfqyp8fdiNPttPT%2FG038.mp4?alt=media&token=295ef769-2101-4901-bf75-ca0aad60236a>" %}

## Before you begin

Read access to the knowledge base and its resource list.

## Key concepts

| Term                   | Definition                                                                                                                                    |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Indexing status        | The reported progress or outcome of preparing a source for search. Check the individual resource when collection totals are insufficient.     |
| Upload                 | Transfer of file bytes through a supported interface or API. Upload acceptance does not establish parsing or indexing completion.             |
| Parsing                | Extraction of usable text or structure from source content. Review the extracted content when the workflow misses text, tables, or locations. |
| Index                  | Searchable records prepared from source content. A file must complete required processing before the index can return its content.            |
| Asynchronous operation | An operation acknowledged before its processing is complete. Retain its handle and follow its documented status or completion mechanism.      |

## Interpret the resource status

| Status                        | Meaning                                                                         | Next action                                                                                  |
| ----------------------------- | ------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| `resource`                    | The source resource is known; this alone does not show that content is indexed. | Check synchronization and processing progress.                                               |
| `pending`                     | Processing is waiting or in progress.                                           | Wait for a later status update before relying on it for retrieval.                           |
| `parsed`                      | Content has been extracted.                                                     | Inspect the parsed text and wait for indexing before relying on indexed search.              |
| `indexed`                     | Content has been prepared for indexed search.                                   | Search for information from the file using the intended user’s access.                       |
| `error`                       | Processing failed.                                                              | Read the file’s error and correct its format, source access, or reported processing problem. |
| `pending_delete` or `deleted` | The resource is being removed or has been removed.                              | Confirm whether it should remain in the selected source set before importing it again.       |

These are resource status values. A whole knowledge base can contain files in different states. An indexed file can still be excluded from a particular query by permissions, source selection, or metadata filters.

## Check whether a source is ready to search

1. Open the resource list and locate the uploaded or synchronized file.

![Use Last synced and Parsed text to check the content currently available for retrieval.](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/6h9Yz821nknHqsYzzAyG/assets/g038-g038-01-baseline.png)

Use Last synced and Parsed text to check the content currently available for retrieval.

2. Inspect its processing state and any error explanation.
3. Query for content from that file after indexing completes.

The file is available to the intended retrieval path.

## Behavior and limitations

A synchronization response of 202 means work was accepted, not finished. Collection totals do not replace checking the target file. If a file is missing from the list, inspect the upload or source selection. If it is listed with an error, resolve the reported parsing or indexing problem before starting another synchronization.

## Related resources

[Sync and ingestion lifecycle](https://docs.stackai.com/guides-and-quickstarts/knowledge-and-retrieval/sync-and-ingestion-lifecycle.md)

[File Inputs, Supported Formats, and Size Limits](https://docs.stackai.com/technical-reference/files-knowledge-and-retrieval/file-inputs-supported-formats-and-size-limits.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/technical-reference/files-knowledge-and-retrieval/indexing-status-and-search-readiness.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
