> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/console/knowledge/faqs.md).

# Knowledge: FAQs & Troubleshooting

Short answers about knowledge bases, datasets, sync, versions and Try Knowledge.

Short answers to the questions people ask most about Knowledge. Each one links to the page that covers it in full.

## Knowledge bases

<details>

<summary>Why doesn't Knowledge expand in the sidebar?</summary>

It has no submenu. Selecting **Knowledge** opens one page: a prompt to create knowledge at the top, and every knowledge base in the project below it as cards. Open a knowledge base by selecting its card. See [Knowledge](/console/knowledge.md).

</details>

<details>

<summary>Where are my datasets?</summary>

Select **All Datasets** in the top right of the Knowledge page. It lists every dataset in the project with its description, number of sources and when it last changed. The datasets a particular knowledge base uses are on that knowledge base's **Datasets** tab. See [Datasets](/console/knowledge/datasets.md).

</details>

<details>

<summary>What is the difference between a dataset and a knowledge base?</summary>

A **dataset** holds source files and tracks their processing. It does not interpret them. A **knowledge base** is what Qore builds from the files in one or more datasets: a table of contents, tags and embeddings that an agent can search. You attach a knowledge base to an agent, not a dataset. See [Knowledge](/console/knowledge.md).

</details>

<details>

<summary>Do I need a dataset before I create a knowledge base?</summary>

No. Describe the knowledge base and attach files in the same step, and Qore sets up what it needs. Create datasets first when you want to reuse the same files across several knowledge bases. See [Create knowledge](/console/knowledge.md#create-knowledge).

</details>

<details>

<summary>Can I share a knowledge base with a colleague?</summary>

Yes, by link. Each knowledge base has its own URL. The person you share it with needs access to the same project.

</details>

<details>

<summary>What happens when I delete a knowledge base?</summary>

The knowledge base and everything Qore generated for it are removed: the table of contents, tags and embeddings. This cannot be undone. The source files stay in their datasets, so you can build a new knowledge base from them. See [Find your knowledge](/console/knowledge.md#find-your-knowledge).

</details>

## Datasets and files

<details>

<summary>Which file types and sizes can I add?</summary>

`.pdf`, `.png`, `.jpg`, `.jpeg`, `.webp`, `.tiff`, `.bmp` and other image formats, up to `15 MB` per file and `25` files per upload. The same formats apply to files from Google Drive. The Agent Builder canvas has a lower limit of `10 MB` per file. See [Create a dataset](/console/knowledge/datasets.md#create-a-dataset).

</details>

<details>

<summary>Why does Google Drive, OneDrive or SharePoint ask me to sign in?</summary>

Cloud sources need your permission before Qore can read your files, so the first time you pick one you authorize Qore with your Google or Microsoft account. If your administrator manages those permissions, ask them before you start.

</details>

<details>

<summary>What do I get when I crawl a website?</summary>

One file, added to the dataset you crawled from, holding every page the crawl reached. The crawl runs in the background. **Maximum pages** (default `25`, up to `200`) caps how much of the site you get, so raise it before you crawl a large site. See [Add a website](/console/knowledge/datasets.md#add-a-website).

</details>

<details>

<summary>What is the difference between Detach and Delete?</summary>

**Detach from knowledge** and **Detach dataset** remove a file or a dataset from one knowledge base. The files stay in the dataset, and other knowledge bases that use them are unaffected. **Delete from dataset** removes the file from the dataset itself. See [File actions](/console/knowledge/datasets.md#file-actions).

</details>

<details>

<summary>Can I download a file I uploaded?</summary>

Yes. In the knowledge base's **Datasets** tab, open the file's **⋮** menu and select **Download original**. To download the text Qore extracted from it instead, open the document's **Raw extraction** tab and select **Download**. See [Document processing](/console/knowledge/document-processing.md).

</details>

## Sync and versions

<details>

<summary>I uploaded a new version of a file. Why is the agent still giving the old answer?</summary>

Uploading changes the dataset, not the knowledge base. The file waits as **Ready to sync**, and agents keep answering from the last synced version until you sync it. Sync the file, wait for **Synced**, and the agent answers from the new version. See [How updates reach agents](/console/knowledge/sync-and-versions.md#how-updates-reach-agents).

</details>

<details>

<summary>What creates a new knowledge version?</summary>

Each file that finishes syncing creates one version, and so does attaching a dataset. Syncing five files gives you five new versions, each named after the file it added. The **vN ▾** menu lists them all. See [Knowledge and file versions](/console/knowledge/sync-and-versions.md#knowledge-and-file-versions).

</details>

<details>

<summary>What is the difference between Ready to sync and Synced?</summary>

**Ready to sync** means the file is processed and in the dataset, but not yet in the knowledge base. **Synced** means the knowledge base answers from it. See [Sync status](/console/knowledge/sync-and-versions.md#sync-status).

</details>

<details>

<summary>What does New version available mean?</summary>

The knowledge base holds an older version of the file than the dataset does. The file counts as *stale* in the **Needs attention** banner. Sync it to bring the knowledge base up to date.

</details>

<details>

<summary>What does auto sync do?</summary>

With **Enable auto sync** on a dataset, files added to it start syncing into the knowledge base without you selecting **Sync**. The dataset shows an **Auto sync** badge. Leave it off where you want to check a file before agents use it. See [Auto sync](/console/knowledge/sync-and-versions.md#auto-sync).

</details>

<details>

<summary>When should I use Force re-sync everything instead of Retry failed files only?</summary>

Use **Retry failed files only** when some files show **Sync failed**. It leaves the rest alone. Use **Force re-sync everything** only when the whole dataset looks wrong in the knowledge base. It syncs every file again, which takes longer and creates a version for each file. See [Sync files](/console/knowledge/sync-and-versions.md#sync-files).

</details>

<details>

<summary>Can I edit knowledge content directly?</summary>

No. To change what a knowledge base says, upload a corrected version of the source file and sync it. Even a one-word fix goes through the file. See [Knowledge and file versions](/console/knowledge/sync-and-versions.md#knowledge-and-file-versions).

</details>

<details>

<summary>Can I roll a knowledge base back to an earlier version?</summary>

No. Earlier versions stay in the **vN ▾** menu, and you can still query them in Try Knowledge, but you cannot make one current again. To undo a change, upload the earlier file as a new version and sync it.

</details>

## Try Knowledge

<details>

<summary>Can I test an older version of the knowledge base?</summary>

Yes. In Try Knowledge, pick the version from the **vN ▾** picker and ask your question. This only affects Try Knowledge. Agents always answer from the latest version. See [Compare knowledge versions](/console/knowledge/try-knowledge.md#compare-knowledge-versions).

</details>

<details>

<summary>What does the Score on a chunk mean?</summary>

How closely that chunk matched your question, from `0` to `1`. Higher is closer. Chunks are listed from the highest score down. See [Inspect retrieved chunks](/console/knowledge/try-knowledge.md#inspect-retrieved-chunks).

</details>

<details>

<summary>What are Execution Report and Evaluation Report?</summary>

**Execution Report**, top right, opens the **Knowledge Chunks and Citations** panel. **Evaluation Report**, under each question, picks which answer the panel shows. A green dot marks the selected answer.

</details>

<details>

<summary>Why does Try Knowledge answer differently from my agent?</summary>

Try Knowledge answers from the knowledge base alone. An agent also follows its instructions and can use its tools and other knowledge, so its answer can differ even from the same chunks.

</details>

## Discovery and search

<details>

<summary>What does Discoverable mean?</summary>

The file is indexed for semantic search over your data sources. While indexing runs, it shows **Preparing for discovery**. Discovery is separate from sync: a **Discoverable** file can still be **Ready to sync**. See [Search and discovery](/console/knowledge/datasets.md#search-and-discovery).

</details>

<details>

<summary>How do I find which dataset has the information I need?</summary>

Use discovery, which searches your data sources by meaning. On a dataset's page, use **Search this dataset**. Or ask in the Knowledge Builder or Agent Builder chat, in your own words. Only **Discoverable** files are found. See [Search and discovery](/console/knowledge/datasets.md#search-and-discovery).

</details>

<details>

<summary>Why doesn't searching find text inside my documents?</summary>

**Search knowledge…** and dataset search match names and descriptions only. To search what documents say, ask the knowledge base in [Try Knowledge](/console/knowledge/try-knowledge.md).

</details>

## Troubleshooting

<details>

<summary>A file shows Sync failed. What should I do?</summary>

Open the **Content** tab and select the file in **Documents** to see the error and the stage it failed at. Then retry: one file from its row, or several with the dataset's **⋮** → **Retry failed files only**. If retries keep failing, the file itself is usually the problem, for example a scanned PDF with no text. Upload a better copy as a new version. See [When processing fails](/console/knowledge.md#when-processing-fails).

</details>

<details>

<summary>What does "3 files need attention — 2 failed, 1 stale" mean?</summary>

Two files failed to sync, and one is out of date in the knowledge base because a newer version exists in the dataset. Select **Review**, or set the filter to **Needs attention**, to see them. See [Resolve items needing attention](/console/knowledge/sync-and-versions.md#resolve-items-needing-attention).

</details>

<details>

<summary>Processing failed with "The provider rate limited the request". Should I retry right away?</summary>

No. An immediate retry usually meets the same limit and uses more quota. The product retries on its own within two hours. If several knowledge bases fail the same way, the limit is probably tenant-wide, so check with your administrator. See [When processing fails](/console/knowledge.md#when-processing-fails).

</details>

<details>

<summary>A file has been Preparing for discovery or Syncing for a long time. What now?</summary>

Wait a few minutes and refresh. While a file is **Preparing for discovery** it shows **Not eligible** for sync, and that clears on its own. Long delays across many files are usually platform-wide, so raise them with your administrator.

</details>

<details>

<summary>Where did Legacy Dataset and Legacy Knowledge go?</summary>

They have been retired and no longer appear in Knowledge. Use datasets and knowledge bases instead. See [Datasets](/console/knowledge/datasets.md).

</details>

### Related

<table data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>Knowledge</strong></td><td>Create knowledge bases and work with them.</td><td><a href="/console/knowledge.md">Knowledge</a></td></tr><tr><td><strong>Sync &#x26; versions</strong></td><td>How file updates reach agents.</td><td><a href="/console/knowledge/sync-and-versions.md">Sync &amp; versions</a></td></tr><tr><td><strong>Datasets</strong></td><td>Add files from uploads, cloud drives or a website.</td><td><a href="/console/knowledge/datasets.md">Datasets</a></td></tr><tr><td><strong>Try Knowledge</strong></td><td>Query any version and see the chunks behind each answer.</td><td><a href="/console/knowledge/try-knowledge.md">Try Knowledge</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.uptiq.ai/console/knowledge/faqs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.