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:

• 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

We most recently opened SalesForce case #16916621 on the heels of SalesForce case #16616931 regarding this issue that has been occurring since January of last year. Our trigger updates had been fairly successful without wholesale changes to any of our triggers for several years until then. SF support ultimately determined that this was a known issue and targeted a fix for first in May 2017, then in December of 2017.

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.

Within the last several days, our cloud has run into a bunch of timeout exceptions when it comes to data processing, exporting SalesForce report data and pulling out information through Apex data loader. This specifically happens usually when we're trying to run or pull out a larger volume of records in the hundreds of thousands or millions. Prior to last week, we had not had such issues with processing or gathering data. The reports tend to lock up during the process executed. Is there anyone that can point to what may be the cause of such timeoutexception errors as of late?

 

The full exception error that we've been seeing involving Apex data pulls reads:

 

java.net.sockettimeoutexception: Read Timed Out

 

Thanks!

Hello,

Have a problem regarding unit tests challenge in apex.Below is my code

@isTest
private class TestVerifyDate{
    @isTest
    static  void TestVerifyDate1() {
        //check for date2 being in the past
        Date day1 = Date.newInstance(2015, 1, 11);
        Date day2 = Date.newInstance(2015, 1, 10);
       
        Date date_res1 = VerifyDate.CheckDates(day1,day2);
        system.debug(date_res1+' Run1: Date1: ' + day1+ 'Date2: ' + day2);
    }  
}

The above code shows an error saying "Method does not exist or incorrect signature: VerifyDate.CheckDates(Date, Date)" . What is the right code please help.


Thanks,
Regards
Deeksha

I need a query which returns the list of records whose lastmodifieddate falls in now() minus 2 mins

 

List<Object> reclist = [Select id from Object where LastModifiedDate =???];

 

Thanks

 

Within the last several days, our cloud has run into a bunch of timeout exceptions when it comes to data processing, exporting SalesForce report data and pulling out information through Apex data loader. This specifically happens usually when we're trying to run or pull out a larger volume of records in the hundreds of thousands or millions. Prior to last week, we had not had such issues with processing or gathering data. The reports tend to lock up during the process executed. Is there anyone that can point to what may be the cause of such timeoutexception errors as of late?

 

The full exception error that we've been seeing involving Apex data pulls reads:

 

java.net.sockettimeoutexception: Read Timed Out

 

Thanks!