> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/center/daylite-mail-assistant/daylite-mail-assistant-has-stopped-responding.md).
# Daylite Mail Assistant Has Stopped Responding
When Daylite Mail Assistant and Apple Mail have stopped communicating, you will receive a message indicating that Daylite Mail Assistant has stopped responding.
If you encounter this issue, try the following solutions:
1. Quit Daylite and Apple Mail.
2. Reopen both applications.
3. Check the email thread again.
If the issue persists, restart Daylite Mail Assistant by following these steps:
1. Quit Mail
2. Click the Apple menu () in the top left corner of your display and choose System Settings.
3. Go to Privacy & Security > Extensions > Added Extensions and turn off the Daylite Mail Assistant (com.apple.email.extension)
4. Restart your Mac
5. Open Mail and turn the extension back on by selecting Settings, then enabling the extension.
If the continues after restarting the Daylite Mail Assistant, please [contact customer support](mailto:support@daylite.app?subject=The%20Daylite%20Mail%20Assistant%20Has%20Stopped%20Responding) for further assistance.
---
# 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://docs.daylite.app/help/center/daylite-mail-assistant/daylite-mail-assistant-has-stopped-responding.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.
