> 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/source-synchronization-updates-and-deletions.md).

# Source Synchronization, Updates, and Deletions

Synchronization copies or updates supported provider content in a knowledge base. The indexed copy can differ from the provider until processing finishes.

{% 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

A valid source connection, supported source selection, and permission to synchronize the knowledge base.

## Key concepts

| Term             | Definition                                                                                                                                      |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Synchronization  | Updating a knowledge base from a connected source. The searchable copy can lag the source until synchronization and indexing finish.            |
| Stale content    | Indexed or displayed content that no longer matches the current source. Check synchronization and processing before changing retrieval prompts. |
| Source selection | The files or folders included in an operation. An empty optional selection can mean the whole knowledge base rather than no files.              |
| Indexing status  | The reported progress or outcome of preparing a source for search. Check the individual resource when collection totals are insufficient.       |

## Synchronize a source

1. Check the selected connection and source files or folders.

![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. Start synchronization through the supported control.
3. Inspect resource changes and processing errors, then confirm that updated content is retrievable.

The knowledge base reflects the completed synchronization and indexing work.

## Behavior and limitations

Removing a file from the provider, removing it from a selection, and deleting a knowledge base are different operations. Their synchronization effects depend on the connector. Check the file list and a fresh query after changes. Previously generated answers do not automatically change when source content changes.

## 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/source-synchronization-updates-and-deletions.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.
