• Get started
  • Documentation

View customer notification logs for your service project

Customer notifications are emails that notify customers about an invitation to join a project or updates on their requests. Sometimes, these notifications don't reach the customer's inbox due to various reasons.

Customer notification logs help project admins see which email notifications didn't get delivered and why. Admins can view all failed notifications in one place and take action to make sure customers receive notifications on time.

Currently, you can only view failed customer notifications.

View customer notification logs

To view customer notification logs, go to your service project, and select Customer notification logs.

Customer notification log details

To view failed customer invites, select the Customer invitations tab.

Each row in the table shows a failed notification. For each notification, you can view:

  • Date and time - When the invite was sent. Currently, the data is only stored for 21 days.

  • Recipient - The email address or name of the intended recipient.

  • Details - The possible reason for the delivery failure.

To view failed notifications related to requests, select the Request notifications tab.

Each row in the table shows a failed notification. For each notification, you can view:

  • Date and time - When the notification was sent following the completion of the action. Currently, the data is only stored for 21 days.

  • Notification name - The name of the notification triggered.

  • Recipient - The email address or name of the intended recipient.

  • Issue key - The key for the issue where the action was performed.

  • Details - The possible reason for the delivery failure.

Common reasons for failed customer notifications

Here are some common reasons why notifications might fail:

  • Internal errors - These happen within Jira Service Management and can cause notifications to fail. Most of these errors are intermittent, so try resending the notification later.

  • Email validation error - This happens when a customer's email address is not formatted correctly. Examples include a missing '@', a comma in the address, or missing angle brackets.

  • Notification template too large - This only affects sites that use paid edition of Jira Service Management. It happens when custom notification templates are larger than 6 MB. To fix this, try reducing the template size and resend the notification. Learn how to edit the content of your customer notifications.

  • Email notifications limit reached - This happens for sites with a limit on email notifications. For example, if you are using a Free plan with a limit of 100 emails per day, then after reaching the limit, Jira Service Management will stop sending notifications until the next day. Learn more about Jira Service Management plans.

  • Email address added to suppression list - This occurs when a customer's email address is blocked due to email bounces or rejections, or if the customer's mailbox blocks emails from Atlassian.

    To fix this error for a failed invite, from your service project, go to the Customers page. Then, search for the customer’s email address and select Resend Invite. The suppressed email address will be removed from the list and an email notification will be sent from Jira Service Management.

  • Private email address - This occurs when you try to invite a customer with an email address from a private network, like someone@192.168.0.217. These addresses can't be used on the public internet. Learn more about address allocation on private networks.

  • Errors from email service providers - Sometimes, Jira Service Management sends an email, but the customer's email service provider rejects it. This can happen if the email address is invalid, the customer's email doesn't exist, or the customer has unsubscribed from notification emails. In these cases, check the error message from the email provider and take appropriate action.

  • Unknown error - Occasionally, customers don't receive notifications due to unknown reasons. If this happens for a customer invite, try resending the invite later.

Still need help?

The Atlassian Community is here for you.