This section will explain what scheduled jobs/tasks are, how you can create and debug them.
Simply put, an Episerver scheduled task is a mechanism within Episerver that you can use run specific code at a specified interval. If you’re looking for a way to execute a certain command several times a day, at a certain time of day, week or, month, then this is what you use. You can create a scheduled Jobs/Tasks by creating a C# class and inheriting the correct attribute to it, like so:
Your custom code will then be run as a background at a specified frequency, time, date etc… One important thing to note is that when you code runs within a scheduled task, it won’t have the same HTTP Context as a normal user. Scheduled tasks will be run by your application pools identify and not a web user, so things like HTTPContext won’t exist. I’ve definitely wasted a few hours wondering why a task worked when I tested it manually (which will cause the HTTPContext to exist) and why it failed when it was scheduled
A Scheduled Job / scheduled Task is the way Episerver provides developers to run some functionality periodically, daily, weekly monthly etc.... This s great for scraping content, updating exchange rates and all sort of other tasks and luckily creatin[...]
The migration of content (also known as "lift and shift") is the process of copying content from an existing platform into the new website. One of the most overlooked phases on a project is the content migration stage. When companies switch CMS plat[...]
When a company decides to power their website using EpiServer, they usually have a content team that updates the website's content on a frequent basis. Despite best intentions, content editors can become a bit lazy when adding new content and forget [...]
Out of the box, Episerver provides a scheduled service solution to cater for any reoccurring tasks that you may need to perform; sending emails, seeding a cache, getting news items from a third party service. Over the years, I've created many a sche[...]