> 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/testing-scheduled-notifications.md).

# Testing Scheduled Notifications

#### Test the Complete Flow

1. Perform the trigger action (book appointment, create task, place order)
2. Check your database to verify:
   * Notification record was created
   * Start Date is correct
   * Notification Job ID is populated
3. If you added a user-facing notification list, verify the notification appears
4. Test adding additional notifications if applicable

#### Test Actual Notification Delivery

To verify notifications actually send at the scheduled time:

1. Create a test record with a notification scheduled for 1-2 minutes from now
2. Wait for the scheduled time
3. On a native device or PWA, verify you receive the notification
4. Tap the notification and verify it takes you to the correct screen


---

# 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/testing-scheduled-notifications.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.