Scheduled jobs

How to fix an issue in Optimizely CMS where the scheduled job «Change Log Auto Truncate» would fail with a timeout.

A couple of months ago Optimizely CMS introduced Deep linking from broken links report to Optimizely edit mode! One problem I discovered was that the «Property Name» does not show up in the Link Status report for existing content until you publish a change. I propose a fix!

In Optimizely CMS 12 the admin mode is given a real facelift. There are graphs and stuff! But is it still the same under the hood...?

A scheduled job is Episerver's/Optimizely's way of running some piece of code at a configurable interval. If there is a chance that code could change in the future, you should add a GUID when you create it!

If you write code that is likely to fail, it is good practice to wrap that section of code in a try-catch-clause and handle the exception. For scheduled jobs, it's the opposite! If something fails, be sure to throw that exception!

Have you ever wondered what your long-running scheduled job is doing right now? Are you waiting for it to finish, and considering if you have time for a coffee? Make your jobs give feedback!

Have you ever wanted to kill a long-running scheduled job? You can! Also, make sure the job restarts if the hosting environment shuts down.

Preventing broken links is an important part of maintaining a website. Episerver's Link Validating job tries to help us, but unfortunately, it has its shortcomings.