[SalesForce] the maximum length for a scheduled job name

The question itself is relatively simple.

If I call System.schedule(String jobName, String cronExpression, Object schedulableClass), what is the maximum length for a scheduled jobname parameter?

The answer wasn't immediately apparent in the System class docs.

As an aside, I'm asking because I've run into a scenario where I need to go to extra lengths to ensure the scheduled job name is unique.

The current code I have takes into account the time when the job was scheduled. However, I've run into a scenario where a subscriber org has spun up all 50 Queueable jobs in one transaction. When each job runs it is trying to schedule another class to run. Depending on the exact timing, some of those resulting jobs end up with the same name. Exceptions are thrown. Jira tickets are raised.

Short of having the Request ID available in Apex to ensure uniqueness I'll need to burn some more characters in the job name. I just need to know how many characters I have to work with.

Best Answer

@sfdcfox beat me to it. However, I got the detail of 255 via:

System.debug(Schema.SObjectType.CronJobDetail.fields.Name);

and looking at the output:

Schema.DescribeFieldResult[...;getLabel=Job Name;getLength=255;...]

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] Need System.schedule cron string for run once

You can do either option (both are viable).

To specify a run-once schedule, specify a fully qualified date and time, such as:

0 0 0 4 JUL ? 2014
| | | | |   | |
| | | | |   | \------- YEAR (2014)
| | | | |   \--------- DAY_OF_WEEK (NOT_SPECIFIED)
| | | | \------------- MONTH (JULY)
| | | \--------------- DAY_OF_MONTH (4th)
| | \----------------- HOUR (0- MIDNIGHT LOCAL TIME)
| \------------------- MINUTE (0)
\--------------------- SECOND (0)

This would run at midnight of the scheduling user on the Fourth of July this year, and never again.

If you want to kill other jobs, you simply query for scheduled jobs that are not already cancelled, and then call System.abortJob on those ID values. See CronTrigger for more information.

Finally, you can also abort the current job in the execute() method:

public void execute(SchedulableContext sc) {
    // Do stuff here
    System.abortJob(sc.getTriggerId());
}

Best Answer

Related Solutions

[SalesForce] Linking CronTrigger sObjects to Scheduled Jobs listings

[SalesForce] Need System.schedule cron string for run once

Related Topic