Just wanted to check if anybody else is experiencing this. Last friday everything was running perfectly. On saturday our instance was upgraded to Summer 19, and on monday we started seeing Apex CPU timeouts in some of our more heavy processes.

Before I start digging to heavily into potential changes on our side, I just wanted to check if anybody else had this too.

  • 1
    I am noticing that today in particular, one of our heavy orgs is getting more CPU limit exceptions than ever before. – Charles T Jun 20 '19 at 0:53
  • 1
    Opened a case with Salesforce. Unit tests that have been running for years are suddenly failing due to Apex CPU Time Limits. Haven't heard anything back yet.... – John Thompson Jun 20 '19 at 1:52
  • Hi and welcome to all new SFSE users. If you found this question via search and are also affected, please do not add a "me too" answer. You're welcome to comment if you have information to add, or write an answer if you can help solve the problem. – David Reed Jun 20 '19 at 11:27
  • Has this also been raised on Trailblazer or Partner Community yet? My first attempt to search for it was not fruitful. – Charles T Jun 20 '19 at 12:26
  • I have received initial feedback from support stating that this is known, but is actually a fix to cpu time not correctly adding up before. I am following up on this and will keep you posted. – Ivar Gunnarsson Jun 20 '19 at 12:54

There is a known issue from Summer '19 where DML operations are contributing towards the CPU limit. Even if there are no triggers on the sObject in question.

See Known Issue: DML Insert operations consumes Apex CPU time

That could certainly have a wide ranging impact across all transactions. If the transactions were already close to the limits this could have pushed it past the edge.

Not the answer you're looking for? Browse other questions tagged or ask your own question.