[SalesForce] Scheduled Apex not consistantly executing, sending emails

I'm having a problem similar to this user's question from about a year ago, although it's not clear to me whether the solution provided there actually resolved the issue (or if it just made the Salesforce UX better-represent the state of things on the Apex Jobs page).

I have a scheduled class that is intended run nightly. It will search through an object to find records where a custom checkbox = True, and then send an email with details about those records to an inbox for archiving. The schedulable class is as follows:

global class ScheduledArchiveProcess implements Schedulable {

    // Runs job every day at 11PM
    private static final String CRON_EXP = '0 0 23 * * ? *';

    global void execute(SchedulableContext sc) {
        new CaseArchiveService().doArchive();
    }

    public static void setSchedule(String name) {
        System.schedule(name, CRON_EXP, new ScheduledArchiveProcess());
    }

    public static void setSchedule(String name, String cronExp) {
        System.schedule(name, cronExp, new ScheduledArchiveProcess());
    }
}

When I schedule the job (either via the UX or via the setSchedule methods above), it will not consistently send emails. I will setup test data and schedule the class, then nothing will happen for days. For whatever reason, several days into the schedule it will then choose to fire off the expected emails, but then will return to not consistently running. The Scheduled Jobs page implies it is running, but I have no emails to show for it.

I can directly run the code via Execute Anonymous and have the code consistently execute, so I don't think that's a problem (although given the number of records in the object we're querying, the SOQL query does take close to a minute to run when I submit via EA).

Given the scenario described above, I have the following questions:

Is there any known reason why a class would run inconsistently when scheduled, despite always running when directly invoked?
Would the solution documented in the aforementioned question – aborting the current job, then rescheduling for a later time – actually address the problem I'm having, or would it just cause the Apex Jobs page to be more explicit about what has/has not been done?
Is there any way to add debugging to a scheduled job that is not being run under a specific user profile (or am I mistaken here and it is being run under a profile)?

I should note that I'm an Apex novice, working with code that was completed (but not turned on) before our previous developer departed, so apologies for any obvious misses or boneheaded statements. Thanks in advance for your assistance!

Update 4/9/15: I suspect this may have something to do with Salesforce timing out the query when initiated via a scheduled job. When I run it via the scheduler, I get up to the query and find the following:

14:00:20.936 (936955661)|METHOD_EXIT|[40]|01pF0000002QxZ2|ArchiveService.getObjectArchiveQuery()
14:00:20.936 (936987788)|SYSTEM_METHOD_ENTRY|[40]|Database.query(String)
14:00:20.940 (940831639)|SOQL_EXECUTE_BEGIN|[40]|Aggregations:0|SELECT [a whole bunch of fields] FROM Case WHERE needs_archive__c = true
14:02:24.902 (124902031857)|SYSTEM_MODE_EXIT|false

However, when I run the same code via Execute Anonymous, it continues past this point:

13:51:44.034 (1034339365)|METHOD_EXIT|[40]|01pF0000002QxZ2|ArchiveService.getObjectArchiveQuery()
13:51:44.038 (1038006973)|SOQL_EXECUTE_BEGIN|[40]|Aggregations:0|SELECT [a whole bunch of fields] FROM Case WHERE needs_archive__c = true
13:53:07.150 (84150020438)|SOQL_EXECUTE_END|[40]|Rows:2

(I've omitted the SOQL SELECT for brevity – it's just grabbing a whole bunch of fields)

Best Answer

Things to think about...

Since the scheduled job has to execute under some user, you can set up debug log for that user and monitor for errors.
There is a limit on outbound Apex emails per day; perhaps some other job has exceeded the limit before the job in question has executed
There could be some query timeout or other catchable exception and the code as written doesn't fail gracefully

With the exception of limit exceptions, asynchronous code should use try-catch to ensure that every exception is caught and some diagnostic log is written for later examination. Such log could be an email to the sysad or and/or writing to a custom Log__c SObject a list of interesting things that happened during the course of execution. Dan Appleman's book 'Advanced Apex Programming' has a good debugging framework worth considering/adapting

Related Solutions

[SalesForce] Linking CronTrigger sObjects to Scheduled Jobs listings

There doesn't currently appear to be any mechanism for determining the apex class or the name of the scheduled job from Apex or via the API (See Ideas:CronTrigger Name field needs to be exposed).

As a stop gap measure, you could create a custom object or setting and manually map from the CronTriggerId returned by System.schedule() and the data that you require (ApexClass name or Id). Reference - Need a way to programatically change or delete a Scheduled Job

[SalesForce] Scheduled Job does not execute. Though shows in GUI

Per SFDC support below is their response that resolved the issue I was having.

I have investigated and found that the issue started happening after 13 because with summer 13 - Scheduled Apex jobs have an AysncApexJob row, this always stays in the Queued status until the job has no nextfiretime, then it gets marked completed, or if the job is aborted, then the AsyncApexJob row gets marked aborted as well. if it is a job that recurs indefinitely, then it will never get marked as completed. It will only get marked completed if after running the execute method, the cron trigger a nextfiretime of null.( see the summer 13 release note -page 229 https://org62.my.salesforce.com/help/doc/en/salesforce_summer13_release_notes.pdf).

Please try to to abort the current scheduled job in the sche duled class and then schedule it after 1 minute. Please see this sample code.

NOTE This is sample code and not ready for production.

global class SFDCselfReschedulingClass implements Schedulable{ 

// Execute method 
global void execute(SchedulableContext SC) { 

// Code to be executed when the schedule class wakes up 

// this section of code will abort the current schedule job 
try { 
system.abortJob(sc.getTriggerId()); 
} catch (exception e) {system.debug('#### schedule job exception while aborting:' + e);} 


// reschedule the job 
system.debug('#### schedule job executing'); 
scheduleNow(); 

} 

global static void scheduleNow() { 

// this section of code will schedule the next execution 1 minute from now 
datetime thisTime = system.now().addSeconds(15); 
integer minute = thisTime.minute(); 
integer second = thisTime.second(); 
integer hour = thisTime.hour(); < br/>integer year = thisTime.year(); 
integer month = thisTime.month(); 
integer day = thisTime.day(); 

String timeStamp = second + ' ' + minute + ' ' + hour + ' ' + day + ' ' + month + ' ? ' + year; 
string jobName = 'SFDCselfReschedulingClass'; 

SFDCselfReschedulingClass p = new SFDCselfReschedulingClass(); 
system.schedule(jobName, timeStamp , p); 

} 

}

I then altered my code to work with the new format provide above:

global class DistiAutomationSchedule implements Schedulable {

    // Execute method 
    global void execute(SchedulableContext SC) { 

    // Code to be executed when the schedule class wakes up 
        AccountPOSTExcelFile.runDistiReports();



    // this section of code will abort the current schedule job 
    try { 
    system.abortJob(sc.getTriggerId()); 
    } catch (exception e) {system.debug('#### schedule job exception while aborting:' + e);} 


    // reschedule the job 
    system.debug('#### schedule job executing'); 
    scheduleNow(); 

    } 


    global static void scheduleNow() { 

    // this section of code will schedule the next execution 1 minute from now 
    datetime thisTime = system.now().addHours(24); 
    integer minute = thisTime.minute(); 
    integer second = thisTime.second(); 
    integer hour = thisTime.hour(); 
    integer year = thisTime.year(); 
    integer month = thisTime.month(); 
    integer day = thisTime.day(); 

    String timeStamp = second + ' ' + minute + ' ' + hour + ' ' + day + ' ' + month + ' ? ' + year; 
    string jobName = 'Disti Automation Schedule'; 

    DistiAutomationSchedule p = new DistiAutomationSchedule(); 
    system.schedule(jobName, timeStamp , p); 

    }


}

Best Answer

Related Solutions

[SalesForce] Linking CronTrigger sObjects to Scheduled Jobs listings

[SalesForce] Scheduled Job does not execute. Though shows in GUI

Related Topic