4

Since last Wednesday one of my schedules jobs (future calendar) does not execute but it schedules next time.I tried to remove and create again the job but was the same. If I execute the Batch manually everything is ok. What can be the problem?

enter image description here

Important: Salesforce schedules the class for execution at the specified time. Actual execution may be delayed based on service availability.

The problem is not the time because in my case when it has to be executed the batch doesnt fire, but do schedule it to next day at the same hour.

Important: Until Wednesday worked fine.

 GRP_ScheduleBatchFutureCalendar schedule = new GRP_ScheduleBatchFutureCalendar();
string sch = '0 00 23 ? * *';
system.schedule('Future Calendar', sch, schedule);
  • Luckly the schedule work again without change anything. It could be a little bug of the plattform – lopez.regalado.fj Oct 18 '15 at 12:20
1

I am not sure the the exact reason but one of the reason could be as per Salesforce documentaion.

To invoke Apex classes to run at specific times, first implement the Schedulable interface for the class, then specify the schedule using either the Schedule Apex page in the Salesforce user interface, or the System.schedule method. **

Important: Salesforce schedules the class for execution at the specified time. Actual execution may be delayed based on service availability.


  • 1
    An out of that what is the reason you are trying to get at? – Eric Oct 17 '15 at 23:56
  • @Eric reason could be anything like issue in code, they may not be calling batch class from scheduler. I thought this could one of the reason. :) – MIX DML Oct 18 '15 at 3:03
0

I ran into a similar issue recently. A scheduled job that queried 500,000 records sometimes showed up as "Aborted" under "Apex Jobs" in Setup. However, it worked fine when the schedule job was launched via apex in the Developer Console.

My best guess as to what was happening is that the Query sometimes timed out.

We tried adding additional conditions in the Where clause, but it still only worked intermittently. Ultimately, we changed the architecture to avoid calling it as a scheduled job.

Hope this info helps.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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