Timeline for How can you avoid hitting 24-hour limits on emails and future calls?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:54 | history | edited | CommunityBot |
replaced http://salesforce.stackexchange.com/ with https://salesforce.stackexchange.com/
|
|
| Dec 13, 2012 at 17:11 | vote | accept | Adam | ||
| Dec 13, 2012 at 17:08 | comment | added | Adam | Great comment, Andrew. Thanks! I personally implement the throttled, scheduled, batched and mixed-type processing. I then use a class factory pattern that handles the appropriate processing depending on the current batch (limited to 1 row per batch with variable processing at each iteration). But regardless, since this is an org-wide concern, clients with other managed packages using up these limits will reduce all resource planning efforts to a "use as little as possible and hope for the best" approach. AsyncApexJob is the way, and the link techtrekker posted has a good example. Thanks again. | |
| Dec 13, 2012 at 9:50 | history | edited | Andrew Fawcett | CC BY-SA 3.0 |
added 10 characters in body
|
| Dec 13, 2012 at 9:23 | history | edited | Andrew Fawcett | CC BY-SA 3.0 |
added 811 characters in body
|
| Dec 13, 2012 at 9:15 | history | answered | Andrew Fawcett | CC BY-SA 3.0 |