Scott Reed
Nov 28, 2018
(7 votes)

Scheduled jobs in the DXC & The Autoheal Policy & Architecture

Scheduled jobs are a great way to write code that can run periodically and perform actions on your CMS or Commerce system through the Episerver API framework I have often used these to much success but in our latest project we needed to do some heavy CRUD syncing of data from 2 of our clients large systems in to the Episerver Commerce catalog structure.

We chose to use Scheduled jobs as we could use the API and we needed to do a few other things, we knew the jobs would be intensive but when we came to test some of this on the DXC we kept getting an issue with our largest fresh import of data.

The jobs were getting aborted, so we contacted Episerver support and were informed that Azure Auto Heal was turned on for the environments. Auto Heal will work out if instances have an issue and restart those instances however one of the thresholds it checks was memory usuage and for us the large fresh import was hitting this issue with memory due to the massive data set we were working with.

There are 2 options for this and around architecturing jobs that will cause heavy processing.

To note Episerver Support told me if you have a commerce site they can create another web app for this at no extra cost.

SO As a thought I'd suggest whenever using Scheduled jobs to consider how much data you are processing and how intensive they are and to consider separating jobs out as standard on the DXC to help mitigate any of these issues.

Nov 28, 2018


valdis Nov 30, 2018 05:02 AM

nais! I just love these healing policies. we are too lame and lazy to deal with high memory usage (or actually it was app intent to use as much as possible and troll GC) but there is always an easy way - just restart damn thing and move on.. :)

Magnus Rahl
Magnus Rahl Nov 30, 2018 02:39 PM

ICYMI there has been a long standing bug in ASP.NET which prevents cache trimming to run correctly, see my blog post here: This results in ever-growing cache when an application runs under memory pressure. Things in epi are cached with timeouts, invalidated when updated etc, but when churning through big data sets it does depend on the LRU algorithm of the cache trimmer to free up memory. The ASP.NET bug has been fixed in .NET Framework 4.7.2 but that fix is still not rolled out to Azure app service in all regions (but should be any day now). 

Please login to comment.
Latest blogs
Optimizely community meetup - Sept 29 (virtual + Melbourne)

Super excited to be presenting this Thursday the 29th of September at the Optimizely community meetup. For the full details and RSVP's see the...

Ynze | Sep 27, 2022 | Syndicated blog

Preview multiple Visitor Groups directly while browsing your Optimizely site

Visitor groups are great - it's an easy way to add personalization towards market segments to your site. But it does come with it's own set of...

Allan Thraen | Sep 26, 2022 | Syndicated blog

The Report Center is finally back in Optimizely CMS 12

With Episerver.CMS.UI 12.12.0 the Report Center is finally re-introduced in the core product.

Tomas Hensrud Gulla | Sep 26, 2022 | Syndicated blog

Dynamic Route in ASP.NET Core When MapDynamicControllerRoute Does Not Work

Background Creating one of the add-on for Optimizely I had to deal with challenge to register dynamically route for the API controller. Dynamic rou...

valdis | Sep 25, 2022 | Syndicated blog