Per Nergård (MVP)
+1
Dec 5, 2012
visibility 3748
star star star star star
(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?

error Please login to comment.
Latest blogs
Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |