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.
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
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