> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/cache-management.md).

# 缓存管理

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-2b16eb157702684a310a422089e04fb7a3f3cdb7%2Fcache_management.png?alt=media" alt="缓存管理"><figcaption><p>缓存管理页面</p></figcaption></figure>

缓存管理用于控制频繁访问数据的自动清除。启用缓存可减少重复的 API 调用，从而提升性能。

## 清除缓存

点击右上角的 **Clear Cache** 按钮，即可立即手动使所有缓存数据失效。

## 缓存表

| 列       | 说明                                              |
| ------- | ----------------------------------------------- |
| **对象**  | 缓存数据的类型（例如，收货缓存、采购订单缓存）。                        |
| **状态**  | 切换此对象的缓存启用或禁用状态。                                |
| **TTL** | 生存时间，以分钟为单位——缓存数据在自动刷新前保持有效的时长。设置为 `0` 可禁用自动过期。 |

## 可用缓存

| 缓存          | 说明                      |
| ----------- | ----------------------- |
| **收货缓存**    | 缓存用于采购订单匹配的收货数据。        |
| **采购订单缓存**  | 缓存采购订单数据，以便在文档处理中更快地查找。 |
| **任务和通知缓存** | 缓存仪表板中显示的任务数量和通知数据。     |


---

# 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.docbits.com/chinese/guan-li-yu-she-zhi/settings/cache-management.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.