By default you can run apex job every 1 hour using cron expression but you can schedule this job 12 times at 5 min duration. However only 100 Apex classes can be scheduled concurrently and 5 batch Apex jobs can be queued or active concurrently.http://resources.docs.salesforce.com/198/10/en-us/sfdc/pdf/salesforce_app_limits_cheatsheet.pdf String sch1 = '0 0 * * * ?';
scheduledQuoteReminderBatchable sqrb1 = new scheduledQuoteReminderBatchable();
system.schedule('Every Hour plus 0 min', sch1, sqrb1);
String sch2 = '0 5 * * * ?';
scheduledQuoteReminderBatchable sqrb2 = new scheduledQuoteReminderBatchable();
system.schedule('Every Hour plus 5 min', sch2, sqrb2);
String sch2 = '0 10 * * * ?';
scheduledQuoteReminderBatchable sqrb2 = new scheduledQuoteReminderBatchable();
system.schedule('Every Hour plus 10 min', sch1, sqrb2);
String sch3 = '0 15 * * * ?';
scheduledQuoteReminderBatchable sqrb3 = new scheduledQuoteReminderBatchable();
system.schedule('Every Hour plus 15 min', sch3, sqrb3);
.
.
.
.
//You get the idea.
.
.
.
.
String sch12 = '0 55 * * * ?';
scheduledQuoteReminderBatchable sqrb12 = new scheduledQuoteReminderBatchable();
system.schedule('Every Hour plus 55 min', sch12, sqrb12 );
There is a simpler approach to scheduling a Job every 5 minutes -- simply create a schedulable job, and then a reschedule routine -- such as that shown below:
global class Case_Escalations_Process_Job implements Schedulable {
global void execute(SchedulableContext context) { // Apex code for the job // As a last step run the RescheduleJob() subroutine shown below: RescheduleJob(); }} public void RescheduleJob(){ // If job currently scheduled remove it List<CronTrigger> SchJobs = [SELECT Id FROM CronTrigger where CronJobDetail.Name = 'Case Escalations Process Job']; String MyJobID; if (SchJobs.size() > 0){ MyJobID = SchJobs[0].Id; // removing the job from the schedule System.abortjob(MyJobID); } // calculating the minute mark which is 5 minutes from now DateTime Cdatetime = DateTime.now(); DateTime NewDateTime; NewDateTime = Cdatetime.addMinutes(5); // Reschedule job in 5 minutes from time job finishes Integer min = NewDateTime.minute(); // scheduling job for a certain minute of the hour String sch = '0 ' + string.valueOf(min) + ' * * * ? '; // rescheduling the job System.schedule('Case Escalations Process Job', sch, new Case_Escalations_Process_Job()); }Hi Radhe,
To schedule an apex class to run every 5 minutes, we do not need to do complex operations like calling schedulable method 12 times after every five minutes.
Instead you can do something simpler:-
for(Integer i=5;i<=60;i+=5){
String CRON_EXP = '0 i * * * ?';
System.schedule('Schedule Class',CRON_EXP,new scheduleBatchApexClass());
}
Hi Radhe,Cron Expression to run a Job every 5 Minutes is given below
If you find your Solution then mark this as the best answer.Thank you!Regards,Suraj TripathiSystem.schedule('Schedule Job Name 1', '0 00 * * * ?', new ScheduleBatchApexClassExample());
System.schedule('Schedule Job Name 2', '0 05 * * * ?', new ScheduleBatchApexClassExample());
System.schedule('Schedule Job Name 3', '0 10 * * * ?', new ScheduleBatchApexClassExample());
System.schedule('Schedule Job Name 4', '0 15 * * * ?', new ScheduleBatchApexClassExample());
System.schedule('Schedule Job Name 5', '0 20 * * * ?', new ScheduleBatchApexClassExample());
System.schedule('Schedule Job Name 6', '0 25 * * * ?', new ScheduleBatchApexClassExample());
System.schedule('Schedule Job Name 7', '0 30 * * * ?', new ScheduleBatchApexClassExample());
System.schedule('Schedule Job Name 8', '0 35 * * * ?', new ScheduleBatchApexClassExample());
System.schedule('Schedule Job Name 9', '0 40 * * * ?', new ScheduleBatchApexClassExample());
System.schedule('Schedule Job Name 10', '0 45 * * * ?', new ScheduleBatchApexClassExample());
System.schedule('Schedule Job Name 11', '0 50 * * * ?', new ScheduleBatchApexClassExample());
System.schedule('Schedule Job Name 12', '0 55 * * * ?', new ScheduleBatchApexClassExample());
global class testScheduleClass implements Schedulable { private final String JOBNAME = 'Repeating Job'; private final Integer FIVEMINUTE =5; public void execute(SchedulableContext cont) { System.debug('every 5 min'); findAndAbortJob(cont); } private void findAndAbortJob(SchedulableContext cont) { if (cont == null) { return; } List<CronJobDetail> cronDetail = [SELECT Id FROM CronJobDetail WHERE Name= :JOBNAME LIMIT 1]; if (cronDetail.isEmpty()) { return; } List<CronTrigger> cronTriggers = [SELECT Id FROM CronTrigger WHERE CronJobDetailId = :cronDetail[0].Id]; if(cronTriggers.isEmpty()) { return; } try { System.abortJob(cronTriggers[0].Id); rescheduleJob(); } catch (Exception e) { System.debug('This was the error ::: ' + e.getMessage()); } } public void rescheduleJob() { Datetime sysTime = System.now().addMinutes(FIVEMINUTE); String cronExpression = '' + sysTime.second() + ' ' + sysTime.minute() + ' ' + sysTime.hour() + ' ' + sysTime.day() + ' ' + sysTime.month() + ' ? ' + sysTime.year(); System.schedule(JOBNAME, cronExpression, new testScheduleClass()); } } Hey there, I know this thread is a bit old, but I figured out a super good way to do this by having the scheduled class reschedule itself every 5 minutes. This way you only have one scheduled job that re-schedules itself every five minutes.There's a video walkthrough here and there's links to my github code example in the video's description: https://youtu.be/NjY51eURQXc Jatin,
Although I wonder if that 100 limit still applies as I no longer see it listed on the governor limits page.
Jatin,
Most of the more complicated solutions are to avoid the error for having more than 100 scheduled jobs. In that it only takes 9 jobs scheduled ever 5 minutes to exceed that. Or 2 jobs scheduled every minute...
https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007T4KWISA3
Here is the way I do this. First I install https://github.com/docbill/Managed-Scheduled-Apex/projects (https://github.com/docbill/Managed-Scheduled-Apex/projects) into my org, and use the quickstart command to schedule with the maximum frequency I need for my batch jobs. At Red Hat we use once every two minutes, because experience has taught us a higher frequency just creates too much locking.
Then I implement my class extending AbstractBatchableBase or AbstractBatchable. The main difference here between just using the Batchable interface, is I can implement a hasWork() method to return false, where there are no records to process, avoiding the batch call. I usually will not hard code constants inside my batch job, but instead allow the constants to be assigned by a json constructor.
Here is a screen shot of scheduled jobs and what type of values we configure:
Notice how we actually can run Cleanup_Batchable under many different input sets for cleaning up different types of records. So it means less code overall. Adding a new cleanup job is typically a 2 point story. The effort is mainly testing to make sure we configured the job correctly.
While the other answers people are giving you are correct, they are only good for a small org with very few scheduled jobs running. You'll quickly find all your available jobs slots are full if you try to schedule many jobs multiple times per hour. Almost all our jobs slots at Red Hat are filled by managed packages, which don't give us the ability to use our managed scheduled apex class.
However, this is also very dark path. As ultimately scheduled jobs eventually are limited in how much they can be scaled. And if you get too many of them, you'll find you start to become bottlenecked.
20 answers
