Recent searches
No recent searches
Notify Requester of Ticket Received trigger ends with error
Posted Apr 11, 2024
Our “Notify Requester of Ticket Received” trigger is failing to send the email to the requester. Checking the ticket events ends with this:
Error
Notification "25821095338125" would exceed limit.
What does that error mean? It appears to only happen when a ticket is unsuspended. Surely that's not by design… can anyone clue me in? Thanks!
0
3
3 comments
Paolo
This occurs rarely when a ticket is recovered from the Suspended View. It triggers an email for user verification, and every CC on the ticket will also receive a verification email. Due to the 20 notification limit being reached between these verification emails and subsequent ticket emails, the error occurred. While this situation is uncommon, it's something to be mindful of when a non-registered end user emails a ticket with several users in CC who are also not registered as end users.
Best,
Paolo | Technical Support Engineer | Zendesk
0
Terry Honn
Thank you, Paolo. That explains what is happening, but not really why. We recently enabled the “Anybody can submit tickets” option and are using the allowlist and blocklist to control from whom we get tickets. Everything appears to be working as we would like, including the sender receiving the verification email as expected, and the ticket getting created and suspended until the sender is verified by clicking the link and setting a password. When they do that, the ticket is recovered and set to new, but the trigger ends with the above error. I've tested extensively, ensuring there are no other CCs on the ticket submission, and even changed the trigger to Notify by > User email — Ticket > {requester}. No CC's there either. Thoughts?
0
Lukáš Kuzník
Hello,
it is also happening when new case is created and our technicians are not receiving notifications….what is unacceptable!
this was not happening in the past but in the last weeks it happens very often.
ZenDesk Engineers - please check last releases in ZenDesk system….maybe something went wrong there or needs to be adjusted a bit.
0