Email notification - Glide list- Maximum number of entries

[praveen_vedula]

Is there any limitation for making the number of entries in a glide list type field. We have a requirement where multiple(number varies) users IDs need to be added to the glide list.

Also, how many users can receive an email sent by Service-Now (email configured in Service-Now) i.e. is there any limitation for the number of entries in the "To" list of the email. If i have an outage communication email that needs to be sent to say 4000 users or more than that (Maximum is 13000), can service-now send it presuming that the process before coming to email notification is in place wr.t. release and deployment.

[#2]

the length of the underlying field of the glide_list is what controls how many it can store (and their total length, obviously).

Generally, if you're expecting something of possibly large, indeterminate length, we would recommend storing in records in a separate table, related to the first record, or not actually storing them at all but 'deciding on the fly'

I don't think there is a technical cap on maximum recipients. Obviously SMTP specifications mean that they'll be broken up into chunks, and that might also depend upon your corporate mail system. But they ought to make it through (as long as it doesn't consider us spammers when a lot of people receive the same email!)

[praveen_vedula]

Hi James, Thank you for the valuable inputs. The issue we are facing is that, we have some users who have already subscribed for communications for which we can get the data from the subscription list. However, there is a need to send out communications like outage or release notes to certain users who have not subscribed who ideally should be subscribing(but due to organizational limitations, they require only few notifications and not all related to an application) Users get the list of people (User IDs) that need to be uploaded into SNOW for a specific release or deployment. is there any easier way to like, download a predefined template from SNOW, update the first column with user IDs and then upload the same document and it should resolve the names. This sounds so fanciful 🙂 as a validation needs to be in place since the user IDs are a combination of letters and numbers. I initially thought a glide list field would suffice assuming the count to be less than 20, but would not be helpful when we have about 6000 users.

[Mark Laucus]

Regarding the second question on the number of recipients for email messages, I have seen that number around 500. When we attempted to send outage notifications to our user groups we could not send them to a user group of 2000 users. What happens is the SMTP sender on the ServiceNow side cannot process that amount of users in one message. I was told if I could batch them into smaller groups that could work.

I think that by design ServiceNow utilizes subscriptions to the configuration items and when events take place to a CI they are notified by the subscription settings. We usually resend the message to our users using our internal mail system once a initial message is created in ServiceNow.

[praveen_vedula]

Thank you very much Mark, that was really some helpful piece of info.