Health Check: Mail Error Queue
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
To use the health check for a mail error queue, upgrade the ATST plugin to at least version 1.53.2.
About the health check
This health check ensures the healthiness of email sending in Confluence Data Center. Emails that couldn't be delivered to a recipient will appear in a mail error queue. Email sending is unhealthy when a mail error queue has any emails.
Understanding the results
Confluence Server
Icon | Result | What this means |
|---|---|---|
| There are no emails in an error queue. | All emails have been delivered to recipients. |
| There is a number of emails in the error queue. | An exact number of emails couldn't be delivered to recipients, and Confluence won't retry sending. An administrator should troubleshoot the issue. Learn more in Troubleshooting. |
Confluence Data Center
Icon | Result | What this means |
|---|---|---|
| There are no emails in the error queue on a particular node. If you get a notification about a failing health check for a mail error queue, verify the other nodes. | All emails have been delivered to recipients from this particular node. |
| There is a number of emails in an error queue on a particular node. | An exact number couldn't be delivered to recipients from this particular node, and Confluence won't retry sending. An administrator should troubleshoot the issue. Learn more in Troubleshooting. |
What happens if I ignore the warning?
Emails in a mail error queue won't be sent to recipients. This means that some users may never get a Confluence email notification intended for them.
Troubleshooting
As an immediate mitigation step, you might consider resending a mail error queue. To do this, go to Administration 
General configuration. Then, go to Mail queue and Error queue. Here, you can either resend or remove all emails in an error queue.
Take this step only as a temporary workaround since it won't resolve the underlying issue with sending emails.
In some situations, manually resending a mail error queue won't help, and emails might still pile up in the error queue. In these cases, don't try to resend the error queue several times. This action will generate more threads for Confluence to process, causing potential performance issues.
To resolve the issues when emails aren't sent from the Confluence, check Mail troubleshooting.
Providing data to Atlassian Support
If you still can't troubleshoot and fix the problem, create a support ticket at support.atlassian.com and attach the requested information. To get support:
Follow the guidelines in Enable mail debugging mode in Confluence Data Center and Server.
Wait for about 15 minutes so that we can collect enough logs.
Go to Administration
> General configuration > Troubleshooting and support tools > Create support zip.Select Customize zip, then select Thread dumps, and select Save.
Select Create zip and download the support zip. In case you have a Data Center cluster, repeat this step for each node.
Attach to the support ticket:
- The support zips