> 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 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://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 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.