Timeline for Apex CPU Time limit exceeded while generating a page/PDF with a LOT of data
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 3, 2020 at 10:29 | answer | added | Shai Fisher | timeline score: 0 | |
| Jul 28, 2015 at 20:48 | comment | added | Keith C | No I don't, hence my comment. This eventually non-optional change is also rolling out which may have a positive or negative effect on your solution. | |
| Jul 28, 2015 at 20:39 | comment | added | Lightning Evangelist | Right now it hits the CPU limit after 4 records. I can convince the users to limit their entry to at most 10 records if need be (or 15 if it works). That should be well under 60,000ms asynchronous limit. But a separate PDF for each is not an option. My point is, I would like to use the full 60,000ms potential asynchronous CPU time, whatever number of records that supports. Because I know at that point that the platform just doesn't support it. Right now I dont know how to get past the 10,000ms limit and utilize the extra that asynchronous transactions offer. Do you? | |
| Jul 28, 2015 at 20:27 | comment | added | Keith C | If the number of records that can be selected is open ended then even if you did manage to find a way to have the 60 second limit applied some selections could exceed that. Also bear in mind the 5M byte limit per email attachment. If you want to stay within the platform compromising on the requirement - e.g. generating a separate PDF per record via a batchable - might be necessary. Otherwise the complexity of calling our to an external PDF service that you create in e.g. Heroku may be needed. | |
| Jul 28, 2015 at 19:09 | answer | added | Mossi | timeline score: 1 | |
| Jul 28, 2015 at 18:56 | review | Close votes | |||
| Jul 29, 2015 at 0:28 | |||||
| Jul 28, 2015 at 17:49 | answer | added | Eric | timeline score: 3 | |
| Jul 28, 2015 at 17:35 | history | asked | Lightning Evangelist | CC BY-SA 3.0 |