Notification problems
Quick answer
Work out why an email did not arrive: conditions, recipients, weight, sending state and the email log.
Key takeaways
- Follow the order: triggered, recipients, sent, delivered
- Zero recipients is the most common cause
- Weight silently suppresses lower priority notifications
- The email log answers most questions in a minute
Check in order
Was the notification triggered, did it produce a recipient list, was it sent, and did the recipient receive it. Each question has a different answer location, and skipping the order wastes time.
Recipient problems
Notifications commonly produce zero recipients.
- The user has no email address or has notifications disabled in their profile
- Send to event creator is off and the event user is the only recipient
- The group has no members with addresses
- Subscription based notifications need the user to subscribe first
Suppression and weight
Weight suppresses lower weight notifications when several fire for the same record, which surprises people who never set it. Also check exclusion lists and whether the notification is marked as active with a valid condition.
Want to learn this properly?
Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.
Check your understanding
Where do you confirm the platform generated a message?
- A. Transaction log
- B. System Logs > Emails
- C. Flow executions
- D. sys_audit
Show answer
B. System Logs > Emails
The email log records generation, state and reason.
Which setting can silently suppress a notification?
- A. Weight
- B. Order
- C. Category
- D. Language
Show answer
A. Weight
Higher weight notifications suppress lower ones for the same record.