Claire_Conant
ServiceNow Employee
When email notifications are missing or slow to arrive, troubleshooting usually starts this way: open the email records, check the sender jobs, and read through logs. It works, but it's slow, and patterns are easy to miss when you're looking at one record at a time. The Email Diagnostics Dashboard gives you the delivery picture all at once. It's a Diagnostics tab inside the Email Notifications dashboard that presents email delivery as a set of recent metrics: queue, jobs, bounces, errors, and account connections. This snapshot helps you see where delivery is falling short and narrow your focus for troubleshooting.
 

Numbers that help you pinpoint the issue

 
The Diagnostics tab evaluates the last six hours of delivery and lays it out as metrics you can refresh on demand. Instead of a single healthy-or-not verdict, it shows the delivery pipeline in parts:
 
  • An email health overview: counts by email status, bounce totals, throughput, and average latency
  • A queue overview: how many emails are send-ready, in retry, or cleared, plus the queue's latency trend
  • A job overview: how the SMTPSender jobs are performing, including sent, failed, currently running, and processing times
  • An error log overview: error counts, the top errors, hard and soft bounces, and blocked addresses
  • Connection status: the real-time state of every configured email account

 

Read together, this data tells you not just whether delivery is failing but where.
 

Claire_Conant_0-1782933806525.png To open the dashboard, go to All > System Notification > Email > Email notifications dashboard, and then select the Diagnostics tab.

 

Data that's organized around the delivery pipeline

 

Email leaves your instance through a pipeline. A message is created, moves to send-ready, gets picked up by an SMTP sender job, and is relayed to your mail server, with retries and bounces along the way. The dashboard mirrors that pipeline. A backed-up queue points to a different stage than a spike in hard bounces or a failing job. Reading the metrics by stage lets you localize the problem instead of guessing at it. The six-hour window keeps the picture recent enough to act on. It's built for what's happening now, not a historical report.
 

Streamlined troubleshooting that starts from what you're seeing

 

Start from what you're seeing and let the matching section point you to the stage:
 
  • Notifications slow or piling up? Check the Queue overview. A growing send-ready count or rising queue latency points to throughput or job capacity, not a broken notification.
  • Sends failing outright? The Job overview shows whether SMTP sender jobs are failing or stalling, and how long they're taking.
  • Specific recipients not receiving notifications? The Error log overview separates hard bounces (permanent) from soft bounces (temporary) and flags addresses that have been blocked.
  • Nothing is sent at all? Connection status shows whether a configured email account has lost its connection.
On a non-production instance, read the numbers against your test configuration before treating them as a problem. If outbound mail is redirected to a single test address or otherwise restricted, the dashboard reflects that setup rather than a fault.
 
Each metric is a starting point, not the full picture. Once the dashboard shows you the stage, the deeper troubleshooting usually lives in your email account configuration.
 

Where to go from here

 

Treat the Diagnostics tab as your first stop when you notice problems with your instance email, or as your go-to for regular check-ins. It shows you which stage to investigate, which usually turns a vague "email is broken" into a specific, answerable question. To reach it, go to All > System Notification > Email > Email notifications dashboard, then open the Diagnostics tab.
 
Once the dashboard becomes your starting point, email investigations tend to move faster. You're working from a picture of the delivery pipeline rather than piecing it together from individual records. The resources below go deeper on any metric that surfaces something unexpected.
 

More info on this topic

 

 

Version history
Last update:
2 hours ago
Updated by: