0

because of the CPU time limit, I'm chaining several Apex calls from an Aura Lightning component using JS promises, hoping that comming back on Front side would end the transaction and reset the CPU time limit countdown. But it is not the case. Is this supposed to not work ? And do you have any idea how to actually reset the Apex CPU time limit ?

Thanks :)

Falzen
  • 1
  • 2
  • This is most likely caused by boxcarring, you can do some reading here: https://salesforce.stackexchange.com/questions/263382/how-to-turn-boxcarring-off-for-lwc-imperative-apex-method-calls – zaitsman Jun 17 '20 at 01:10
  • 1
    @zaitsman Precisely! Good to know, thanks. We ended up manipulating the page just a bit between critical calls (switching a display of nothing ON and OFF). That seems to truely complete the transactions and enforce the synchronicity (and unicity) of the multiple Apex calls (still around 10 seconds of loading for the page but it should be slightly better in a production org). – Falzen Jul 01 '20 at 09:29

0 Answers0