Salesforce Batch Job Cron
Expression Generator

Understanding Salesforce Apex Cron Syntax & Scheduling Mechanics

Unlike standard Linux cron syntax, which uses 5 parameters, Salesforce uses a specialized 6-to-7 parameter Quartz cron format: Seconds Minutes Hours Day_of_Month Month Day_of_Week Optional_Year. Understanding special characters like ?, *, L, and # is critical to avoiding overlapping batch execution and system lockouts.

Best Practices for Scheduling Apex Batch Jobs

Scheduling Batch Apex lets organizations automate large-scale data processing, nightly integrations, and system maintenance outside peak business hours. Implementing scheduled jobs requires balancing automated schedules with Salesforce platform architecture and execution rules.

Key Rules & Governor Limits to Keep in Mind

• Concurrent Job Limits: Salesforce enforces a limit of 100 concurrently active scheduled Apex jobs per organization.
• The Question Mark Rule: Day of Month and Day of Week cannot both be specified. If one is defined, the other must be a question mark.
• User Timezone Dependency: Scheduled jobs run according to the timezone of the user who submitted the schedule.
• Flex Queue Staggering: Stagger overnight batch classes by 15 to 30 minutes to reduce concurrent processing bottlenecks.
• Monitoring & Managing Jobs: Review scheduled executions in Salesforce Setup under Scheduled Jobs or query them through the Developer Console.

Example: A Batch Class You Can Schedule Directly

The simplest setup is one class that implements both interfaces, so the same class can be run on demand or on a schedule:

global class LeadSyncBatch implements Database.Batchable<SObject>, Schedulable {
    global void execute(SchedulableContext sc) {
        Database.executeBatch(new LeadSyncBatch(), 200);
    }
    global Database.QueryLocator start(Database.BatchableContext bc) {
        return Database.getQueryLocator('SELECT Id FROM Lead WHERE Status = 'Open'');
    }
    global void execute(Database.BatchableContext bc, List<SObject> scope) {
        // process this chunk
    }
    global void finish(Database.BatchableContext bc) {}
}

Then paste the generated System.schedule() line into Anonymous Apex. Lower the scope size (the second argument to executeBatch) if you hit CPU or heap limits, or if the job calls out to an external system.

Monitor and Remove Scheduled Jobs

// List active schedules
SELECT Id, CronJobDetail.Name, State, NextFireTime, CronExpression
FROM CronTrigger WHERE State != 'DELETED'

// Stop one
System.abortJob('08e...');

Common Mistakes We See in Salesforce Orgs

These come from cleaning up scheduled automation across the implementations and audits we have done — not from the documentation:

• Jobs owned by a person who left. Schedules run as the user who created them. Use a dedicated integration user so deactivating an employee does not silently stop your nightly sync.
• No failure alerting. Salesforce does not notify anyone when a batch chunk fails. Nobody finds out until reports look wrong. Log errors to a custom object or send an email from finish().
• Everything scheduled at midnight. Ten jobs at 12:00 AM means most sit in the Flex Queue because only 5 batch jobs run at once. Stagger them.
• Schedules lost after a sandbox refresh. Keep scheduling scripts in source control so they can be re-run in minutes.
• Using Apex when a Flow would do. A scheduled-triggered Flow handles simple nightly updates without code or deployments. Reach for Batch Apex when you are processing tens of thousands of records or need chunk-level control — not for ten-record updates.

Related Free Tools & Services

• Salesforce Implementation Cost Estimator — budget a project before you scope it.
• Salesforce License Advisor — check whether you are on the right edition and seats.
• Salesforce Integration Services — when scheduled jobs are really an integration that needs a proper design.