Triggered Send | Auto-retry that results in completed send does not reset error count resulting in paused Triggered Sends
Last updated 2021-04-27 ·Reference W-8880092 ·Reported By 1 users
Currently when an auto-retry occurs that results in a Triggered Send job successfully sending again, the overall error count for the Triggered Send is not reset. After some time this will result in the error count threshold being reached that will pause a Triggered Send despite it being able to successfully be restarted.
This results in Triggered Send queues building and Triggered Sends being unexpectedly paused.
There is not a straightforward way to replicate this outside of having a Triggered Send that produces a large number of emails and occasionally runs into intermittent time out issues.
If you receive a Alert Manager notification containing the error class "OMM_SENDERR" you can go ahead and restart the Triggered Send through the UI or via API.
Reported By (1)
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.