Skip to main content

Error: Compile Error: Schedulable class has jobs pending or in progress

Today, while working on one of class, when I tried to save my changes I got following error:-

 Error: Compile Error: Schedulable class has jobs pending or in progress at line 5 column 21

I thought, its coming because there may be some job is running or scheduled. However, when I checked Setup >> Build >> Jobs >> Scheduled Jobs, I couldn't find any scheduled job. Just to be sure that there is not any apex job in running status I checked Setup >> Build >> Jobs >> Apex Jobs. And there were not any job in running status. 

 Just to be clear, Apex Jobs were listed in descending order of Submitted Date. I just checked first few of Apex Jobs. They were either in Aborted or Completed status.

 I was wondering what's wrong. After further analysis, I decided to check Setup >> Build >> Jobs >> Apex Jobs in more detail. After scanning status of all Apex Jobs, I found one job which was still in 'Queued' status. And it's Submitted Date was 15 days older. Something might have went wrong and this job got stuck in queue only.

 Next question was, how to get rid of this stuck job. I thought of deleting this job by deleting this record from 'AsyncApexJob' object. However, we can't update or delete record from 'AsyncApexJob'.

 The other option I found after further exploration, is that there is a method 'System.abortJob()', which change the status of Apex Job from 'Queued' to 'Aborted'.

 We as developer, can use 'Developer Console' to get rid of stuck job using above method.

Comments

Post a Comment

Popular posts from this blog

Mashup Integration in Salesforce

During preparation for TA certification exam, I came across a word Mashup for integration a number of times. I explored about it and below is description:- Mashups, sometimes called “composites,” are hybrid applications created by bringing together several data sources and Web services to create a new application or to add value to an existing application. Behind the scenes, mashups may require different levels of integration, depending on whether the mashed-up data is only meant to be viewed, whether it can be edited, and whether data is actually transferred between systems. There are three types of mashup:- Client Presentation Mashup - In this type of mashup the integration takes place strictly at the visual level. It makes possible to view data from two or more applications in a browser,  without actually moving data between the applications. Example - Google Maps. Client Service Mashup - As mashups evolve, they are becoming more complex and sophisticated. Client...
16 comments
Read more

Make Calls to PageReference.getContent() in Asynchronous Apex - Winter16

You can now make calls to the getContent() and getContentAsPdf() methods of the PageReference class from within asynchronous Apex such as Batch Apex, Schedulable and Queueable classes, and @future methods. This allows you to design much more flexible and scalable services that, for example, render Visualforce pages as PDF files.
5 comments
Read more

Hierarchical Relationship

Recently, I came across one of requirement where client wanted to have a custom lookup field on User object. This lookup will be on User. Based upon certain criteria, value of this field will go to Manager field. They didn't want update of Manager, but on the basis of some business use case. First impression to me was it will be straight forward to create a lookup on user and then in trigger will check for business use case and update Manager field accordingly. However, when I proceed with creating a look on User object, I couldn't find an option ' Lookup Relationship ' on first screen of 'New Custom Field'.  In fact, I saw only available option ' Hierarchical Relationship ' for creating any sort of relationship. I know most of us know about it. But you can't defer on my opinion that we tend to forget these small stuff. Since, on user you can't have any direct relationship, but only user. Salesforce gives you special relationship data t...
6 comments
Read more