Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Is there a way to monitor scheduled jobs?

We have an on-premises installation of ServiceDesk that requires the ability to process incoming emails. Over the last few months, the following Scheduler Administration jobs have intermittently stopped running:


This causes comments sent via email not to be added and other problems. The only solution is to restart the application. We have a support ticket open with Atlassian to resolve the problem, but in the meantime, does anyone know a way to monitor those services and trigger a notification when they fail? Recommendations for add-ons or Groovy scripts welcome. (We have Scriptrunner, Extension for JSD, and JSU Automation Suite available)



1 answer

Hello Ron,

Did you find any way to monitor scheduled jobs?. We are having the same issue and we would like to get some kind of notification at least, so we will know when the processor has stuck.


Best regards,

Francisco González

Hi @Fgon87 no we never came up with anything. The problem still occurs intermittently. The only pattern we've seen is the problem is more likely to occur at times when the database is offline for maintenance. But it doesn't always happen when the database is offline and sometimes it happens when the database is online. How about you?

Hello @Ron Coulter

Our situation its different. The problem is that MailProcessorJobRunner gets stuck when trying to process some emails. These emails have lots of "Chunks" and the only solution is to go through the database and change the status of those emails to "FILTERED" so Jira ignores them and then restart Jira to restart processing.

In your cases it looks like it is enough by restarting Jira.

In both case what we need it is some notification to avoid been checking the processor every day/hour. Of course if it possible with script runner it could be so much better for us. We also have several plugins running because this is a big instance.

@Ron Coulter If you find out about any kind of notification please let us know. It would help us a lot,


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events