Apex Code Development You need to sign in to do that
Don't have an account?
jmurty CPU time limit issues
I had previously opened a couple cases since last year in regards to errors in our Data Loader jobs in violation of the CPU time limit governing limit connected to some of the triggers in our Account object. These errors mainly come in two identified scenarios:
As of now, we are still getting a wide swath of CPU time limit errors on many of these trigger related batches despite the targeted fix schedule. Is anyone else noticing that these issues are now popping up or have they made any updates to the specific known issue we're experiencing before we end up posting another case?
The main known issue was that SalesForce was using a CPU time limit for triggers of 10000 milliseconds instead of the stated asynchronous trigger time limit of 60000 milliseconds.
- Upon creation of an Account that has Latitude and Longitude coordinates
- Upon any account change that results in a change of ownership whether
- a direct change of the field through data loader
- an indirect change through one of our account triggers
As of now, we are still getting a wide swath of CPU time limit errors on many of these trigger related batches despite the targeted fix schedule. Is anyone else noticing that these issues are now popping up or have they made any updates to the specific known issue we're experiencing before we end up posting another case?
The main known issue was that SalesForce was using a CPU time limit for triggers of 10000 milliseconds instead of the stated asynchronous trigger time limit of 60000 milliseconds.