> For the complete documentation index, see [llms.txt](https://developers-apps-in-toss.toss.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers-apps-in-toss.toss.im/guide/zh/operation/check.md).
# 设置紧急维护
合作方可以在控制台中提前设置小程序服务维护日程，向进入维护中的小程序的用户展示小程序服务维护通知。
使用维护功能时，用户在访问小程序时会看到告知维护状态的页面。
{% hint style="info" %}
**请务必确认。**
* 请在维护开始前提前设置维护通知。
* 维护结束后必须将状态更改为“取消”。即使小程序已经恢复正常，维护通知也可能会持续展示。
* 维护期间无法请求审核发布最新版本。
{% endhint %}
{% hint style="info" %}
**对正在使用中的用户的处理**
当前维护设置仅在小程序 **进入时**才会展示维护通知。对于已经在使用小程序的用户，在 Apps in Toss 中也无法确认其状态。
因此，如有需要维护， **需要提前公告及单独措施**。
如果与自有服务器的通信中断，建议在客户端也显示弹窗，并实现结束小程序的逻辑。关于结束小程序，请参考 closeView。
{% endhint %}
### **紧急维护设置访问**
* **访问方法：** Apps in Toss 控制台 → 选择工作区 → 选择小程序 → 应用信息 → 右上角 **`告知紧急维护`**
### **输入紧急维护日程**
* **维护开始时间 / 结束时间：** 请准确设置维护进行的期间。
### **结束并修改紧急维护日程**
* 再次点击已设置的维护设置菜单，即可取消维护日程。
* 取消后，向用户展示的维护通知会立即消失。
* 如果需要延长日程，也请点击“紧急维护预定”按钮修改日程。
### **维护相关小程序展示界面**
当紧急维护开始时，在访问服务时 **“服务正在维护中”** （左侧页面）会展示。 \
在该页面中可以选择是否同意接收维护结束通知，已选择接收通知的用户在紧急维护结束后会自动收到推送/通知。（右侧页面） \
从 Toss App 5.253.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 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://developers-apps-in-toss.toss.im/guide/zh/operation/check.md?ask=&goal=
```
`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.
