Per Nergård (MVP)
Dec 5, 2012
  3664
(1 votes)

Monitoring status of scheduled jobs

Scheduled jobs are a convenient way of performing different tasks in an automated way.
Since it's common that jobs performs something with pages it's not uncommon that something changes so the job will break.

A website admin should check the status of the active jobs on a regular basis, but my experience is that's not very common.

So finding out about a failed job usually take unnecessary long time.
I decided that I wanted to do something about it so I created a scheduled job that will perform a check on all active jobs and report back which ones have failed.

Ok it will not find out if someone disables a job or disables the actual scheduler service but it’s good enough for me.

The monitoring job sends out an status email.

The email recipients are specified on a string property on the start page. Several addresses can be separated with comma signs.


Three different mails are sent out.


1. Failed jobs found
The mail contains a descriptive text and a table with two columns: name of the failed job and the error message.
2. No failed jobs found
The mail contains a descriptive text that everything seems fine.
3 The monitoring job it selves crashes for some reason
Basically the same as .1. The descriptive text says that the job monitoring the others has failed and someone needs to have a look.

The job is built for CMS6 and is easy to get to work for CMS5 and I don’t now but my guess is that it will work for CMS7 with no changes.

You can get the source code over at the code section.

Happy monitoring!

Dec 05, 2012

Comments

Isabella Gross Alström
Isabella Gross Alström Oct 14, 2020 01:17 PM

This is exactly what I am looking for - but the code section link is no longer working :( Do you have this code still somewhere?

Please login to comment.
Latest blogs
Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |