I have a unit test, where im testing, if the class, which implements Schedulable interface is being scheduled using System.schedule() method. The problem is, that when Running this test class, it creates ApexAsyncJob and now i can't modify that test class. Im getting "This schedulable class has jobs pending or in progress" error upon saving the class.

enter image description here

The test method looks like this:

public static void testScheduleJob() {

       Id cronJob = OrderResubmitService.scheduleJob();  

And the OrderResubmitService method looks like this:

public static Id scheduleJob() {
    OrderResubmitSchedulable ors = new OrderResubmitSchedulable();
    String sch = calculateNextCronTime();

    return System.schedule(CRON_JOB_NAME, sch, ors);          

Schedulable class:

global class OrderResubmitSchedulable implements Schedulable {    

    global OrderResubmitSchedulable() {


    global void execute(SchedulableContext SC) {        


    private static void resubmitOrder() {

        // make an http-call      
        String msg = OrderUtilities.submitOrder();

        // check if order is still being processed by SAP        
        if (msg == '202' || msg == '210') {
            // check if we have still some attempts left and we dont have already 100 scheduled jobs
            Boolean governorLimitOK = OrderResubmitService.canScheduleAnotherJob('OrderResubmitSchedulable');
            if (governorLimitOK) {                    
  • Can you please edit your post to add more detail justifying your conclusion these jobs were created from a test? If that is indeed what happened here, it's a bug. No data should persist from your test runs. It's extremely rare, but it wouldn't be the first time...see also: Changing username in Apex Test is emailing the user
    – Adrian Larson
    Jan 12, 2017 at 14:32
  • It would also be helpful if you share what instance you are on and some Minimum Viable Reproduction, in other words Apex code anyone could drop into any org to reproduce for themselves.
    – Adrian Larson
    Jan 12, 2017 at 14:38
  • is it better? its nothing complicated Jan 12, 2017 at 14:39
  • 1
    Technically, your MVR is not complete without the Schedulable class also.
    – Adrian Larson
    Jan 12, 2017 at 14:40

1 Answer 1


I suspect you have an instance of the Job running outside of the testing context.

Try the following SOQL query:

Select Id,JobType,ApexClassId, ApexClass.Name, Status,JobItemsProcessed,TotalJobItems,NumberOfErrors,CompletedDate,MethodName,ExtendedStatus,ParentJobId,LastProcessed,LastProcessedOffset from AsyncApexJob where Status not in ('Completed', 'Aborted')

I tried your sample test method and class and couldn't get it to lock up the associated classes. Even with the future method rescheduling the class.

  • Running instance outside of testing context should be isolated...in another day it worked as It should. Feb 21, 2017 at 14:19

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .