DFE 1.0.0 - 10 Understanding the Scheduled Jobs

Owned by Allan Thraen
Last updated: Jun 24, 2019
2 min read


Digizuite Warm Up

The Warm Up job, typically runs automatically on site initialization (configurable) and will 'warm up the cache' meaning that it will fetch and cache the first batch of assets in every folder to ensure the editorial experience is fast.

In the configuration, you can modify the "autowarmup" parameter of the "digizuite" element to decide if it should be run on startup or not. The advantage of running automatically is that future navigation will be faster - the disadvantage is that startup will be a little bit slower.

Learn more about the configuration parameters here: DFE 1.0.0 - 3 Setting up Episerver


Digizuite Sync Job

The Sync job will call Digizuite and get changed/updated/removed assets since it was last called. Then, it will remove those assets from cache - as well as alert other Episerver front-end servers to clear their cache for those items.

This is a fairly lightweight job and can easily be configured to run very frequently (every few minutes - or even every 30 seconds).

This scheduled job activates the GetListItemChanges method on the Digizuite Client object. This in turns sends off a request through the Digizuite SDK to perform the search on Digizuite called "GetModifiedAssets", which then retrieves a list of assets that have changed and should be removed from cache.


Digizuite Rebuild Cache

This scheduled job will try to load all assets in the various Digizuite folders and cache them on Episerver for fast access.

This can be useful for example if you have switched DAM Centers and need to clear the cache and fill it with new assets. Learn more about switching DAM Centers here: /wiki/spaces/DD/pages/695763046