> 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/troubleshooting-scheduled-notifications.md). # Troubleshooting Scheduled Notifications **Job ID is not storing:** * Verify date format is set to "No Formatting" in Schedule Notification setup. * Check that Update Notification action runs after Schedule Notification action. * Ensure you're referencing `Scheduled Notification > Job ID` correctly via MagicTect **Notifications not appearing in list:** * Verify Related Record relationship was created correctly. * Check that list filter is correct: `Related Record = Current Record` * Confirm notification records are in your database **Notification not sending at scheduled time:** * Check that date format is "No Formatting" (not "relative") * Verify the Start Date calculation is correct * Ensure user has notification permissions enabled * Check that user has been active in app within last 2 weeks * Body of notification is empty. you must fill out the body of the notification or the notification will fail to send. --- # 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/troubleshooting-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.