Timeline for CPU Timeout limit exceeded exception caused for existing working code after SF upgraded to Summer'16,. Any idea if anything updated in Summer'16
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 21, 2016 at 11:27 | comment | added | Mr.Frodo | Probably you can check debug logs what components exactly are running in a transaction. | |
| Jun 21, 2016 at 11:25 | comment | added | Garima Kour | No. Customers have not yet reported this one. We found out this during our testing. And no other packages are installed. We will be optimising our code to handle this but wanted to make sure if Summer'16 has changed something because its the older code working for years with the same amount of data. | |
| Jun 21, 2016 at 11:23 | comment | added | Mr.Frodo | It could be possible that they have installed some other packages or they have some custom code written on there side which is adding with your transaction. | |
| Jun 21, 2016 at 11:15 | comment | added | Garima Kour | It will be difficult to provide the whole codebase here. We parse a csv with approx 5k values and create the XForm. The limit which we had provided to our customers was this and it was working fine from last 2 years and now it suddenly stopped working. We didn't even change the codebase. | |
| Jun 21, 2016 at 10:51 | history | edited | Mr.Frodo | CC BY-SA 3.0 |
added 6 characters in body
|
| Jun 21, 2016 at 10:41 | history | answered | Mr.Frodo | CC BY-SA 3.0 |