1

I have a code which was working for my previous packages. But after the Summer'16 release I am getting the CPU timeout exception for my codebase which was working earlier. Is there any thing update from SF side in summer'16. Because the codebase has not been changed and I suspect something in the release is causing this.

Improve this question
4
  • 1
    The cause of CPU time out could be increase in Data also.So probably you need to consider that as well.
    – Mr.Frodo
    Commented Jun 21, 2016 at 9:36
  • Yes Its considered. But previously also it was working with the same amount of data.
    – Garima Kour
    Commented Jun 21, 2016 at 9:37
  • We are facing the same issue, you able to find the root cause ??
    – Amit Kumar
    Commented Feb 8, 2017 at 13:40
  • @AmitKumar Unfortunately no. SF said that they have backend changes to improve quality. We had to handle it our end.
    – Garima Kour
    Commented Feb 9, 2017 at 14:48

2 Answers 2

Reset to default
0

Summer-16 release notes:

Actually with summer-16 they have improved the other cross-namespaced limits.

but the Limits that are shared across all namespaces, such as the limit on maximum CPU time, remain the same. The new cumulative limit doesn’t affect these limits.

I don't think there is any direct reason or change which can start causing the CPU timeout exception.Maybe you can provide detail of supporting code sample etc maybe that is helpful

Improve this answer
4
  • 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.
    – Garima Kour
    Commented Jun 21, 2016 at 11:15
  • 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.
    – Mr.Frodo
    Commented Jun 21, 2016 at 11:23
  • 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.
    – Garima Kour
    Commented Jun 21, 2016 at 11:25
  • Probably you can check debug logs what components exactly are running in a transaction.
    – Mr.Frodo
    Commented Jun 21, 2016 at 11:27
0

This was raised with SF, and they said they make improvements to limits in backend and don't mention these in release notes. We had to change our entire code flow to handle this

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .