ServiceNow Hidden Gem #7: The Bounce Email Address Table Uncovered

In this episode of ServiceNow Hidden Gems, we explore a system table that can silently break your notifications — sys_blocked_email_address.

Have you ever seen a situation where your notification triggers correctly, logs look fine, but the user never receives the email?

One possible reason is that the email address is present in this table.

The sys_blocked_email_address table is used by ServiceNow’s email engine to block outbound emails to specific addresses. Once an address is added here, ServiceNow will stop sending emails to it, even if your notification logic is perfectly valid.

In this video we cover:

• What sys_blocked_email_address is
• How ServiceNow decides to block an email address
• A practical demo using an invalid email and repeated bounces
• How entries get created automatically after multiple failures
• Why this table is critical when debugging email issues

In the demo, we intentionally send emails to an invalid address multiple times. After repeated failures, ServiceNow automatically adds the address to this table, and all future emails to that address are silently blocked.

If you work with ServiceNow notifications, email engine, or platform debugging, this is something you should definitely be aware of.

Previous videos in the Hidden Gems series

01 – Evaluate Script API
https://youtu.be/ryeDWM2-G2w

02 – GlideRecord.setForceUpdate()
https://youtu.be/oJm4zePEcH8

03 – GlideAggregate.addHaving()
https://youtu.be/7S1_uLn3deI

04 – GlideRecord.setUseEngines()
https://youtu.be/kmIgWcdCHWQ

05 - GlideRecord.addExtraField()
https://youtu.be/9Vu2I3SqWVg

06 - gs.eventQueueScheduled()
https://youtu.be/eP1BoejySBs

Subscribe for more ServiceNow tips & tricks! 🚀

#ServiceNow
#ServiceNowDeveloper
#ServiceNowTips
#ServiceNowDevelopment
#ServiceNowEmail
#ServiceNowNotifications
#ServiceNowDebugging
#SNOWDeveloper
#ServiceNowCommunity

Видео ServiceNow Hidden Gem #7: The Bounce Email Address Table Uncovered канала loop91 - ServiceNow