Timeline for SINGLE_EMAIL_LIMIT_EXCEEDED. What does it mean?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 26, 2018 at 9:25 | history | edited | Pranay Jaiswal | CC BY-SA 4.0 | Update. links and number of emails sent/ |
| May 26, 2018 at 9:17 | history | edited | Pranay Jaiswal | CC BY-SA 4.0 | edited body |
| Jan 28, 2014 at 18:08 | vote | accept | edgartheunready | ||
| Jan 28, 2014 at 15:18 | comment | added | edgartheunready | Messaging.reserveSingleEMailCapacity() didn't seem to work. It was not throwing an exception when I called it. | |
| Jan 28, 2014 at 15:17 | comment | added | edgartheunready | Email is working now. Looks like I hit a daily org limit. | |
| Jan 27, 2014 at 22:11 | comment | added | edgartheunready | Looks like I will have to wait until tomorrow and see if that is the issue. (I have a sneaking suspicion that it is.) In the mean time, I will add that exception handling. | |
| Jan 27, 2014 at 22:04 | comment | added | sfdcfox | As a side note, you can gracefully catch the error with Messaging.reserveMassEmailCapacity and Messaging.reserveSingleEmailCapacity, which lets you catch exceptions when your organization would be exceeded. You can either back off the number sent, or inform the user that there are insufficient messages remaining. | |
| Jan 27, 2014 at 21:57 | history | answered | Michael Welburn | CC BY-SA 3.0 |