> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/actions/notifications/scheduled-notifications/view-scheduled-notifications.md).
# View Scheduled Notifications
Monitor and manage your app's scheduled push notifications directly in the Adalo editor.
You can view scheduled push notifications for each of your apps directly in the editor. Use this to monitor active notifications, review past notifications, and troubleshoot any delivery issues.
***
#### How to Access
1. Open your app in the Adalo editor.
2. Click the **Settings** tab in the left panel.
3. Scroll down to the **Scheduled Notifications** section.
4. Click the green **View Scheduled Notification** button.
A panel will open with two tabs: **Active** and **History**.
***
#### Active Tab
The **Active** tab lists all scheduled notifications that are pending. They have been set up but not yet sent or completed.
Click on any active notification to open its details, where you can:
* **Edit** the notification (update the message, timing, date, or number of times to repeat)
* **Cancel** the notification to prevent it from sending
{% hint style="warning" %}
Once a scheduled notification has been cancelled, it cannot be reverted.
{% endhint %}
***
#### History Tab
The **History** tab shows a log of all past scheduled notifications.
If a notification has a failed status, click on it to view the error message. Review your notification setup to identify the issue. Check that your action trigger, timing conditions, and target collection are all configured correctly.
***
#### Help
If notifications continue to fail, reach out to [Adalo Support](https://info.adalo.com/submit-a-support-ticket) with a screenshot of the error message, and someone from our team will take a closer look.
---
# 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://help.adalo.com/actions/notifications/scheduled-notifications/view-scheduled-notifications.md?ask=&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.
