Throttled jobs with no throttle limit throws 'NullReferenceException'
Last updated 2020-09-29 ·Reference W-7139766 ·Reported By 0 users
In some scenarios clients may receive notifications for cancelled actions that reference OMM.OMMSlot.ReleaseThrottledSlot in the failure message. In these scenarios the job will be placed in a cancelled state.
Pause a Triggered Send that has a Throttle specified.
For Triggered Sends clients will be able to edit the throttle to an unattainable upper limit such as 100 million and then restart the job. For bulk sends there is not a work-around for this.
Reported By (0)
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.