> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/global-settings/email-notification/troubleshooting.md).

# Troubleshooting

These are some tips and additional delayed notification troubleshooting steps you can take to resolve delays in notification delivery:

## Delayed notifications:

* **Check network delays**:
* Make sure the network over which notifications are sent is not congested or disrupted. Network problems such as packet loss or delays can affect email delivery.
* **Email Queue Monitoring:**
* Check the email server queue to determine whether notifications are being queued and sent properly. A large number of emails in the queue may indicate problems with the email server.
* **SMTP configuration verification:**
* Verify that the SMTP configuration is correct and that the email server is properly configured to send outgoing emails. Check the authentication settings and server address to ensure they are correct.
* **Check firewalls and security settings:**
* Check firewall settings and other security settings to ensure that the email server is properly configured to send outgoing email and that no ports used for email are blocked. Shipping is required.
* **Server utilization check:**
* Check the utilization of the server hosting the document management system to ensure that there are no resource bottlenecks that could affect the delivery of notifications.

By performing these additional checks, you can identify potential causes of delayed notifications and take appropriate action to optimize notification delivery and ensure users are informed in a timely manner.

\\


---

# 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.docbits.com/administration-and-setup/settings/global-settings/email-notification/troubleshooting.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.
