After creating the project with Empty Episerver site using Episerver CMS Visual Studio Extension version 126.96.36.1990, updated the EPiServer.CMS Nuget packages to version 11.10.1 and checked the default schedule jobs that were defined:
The default scheduled jobs that are out of the box and their configuration are:
- Link Validation (Inactive)
Checks links on the website to identify broken links with the Link Validation job. The system tries to contact the target for the link to verify that it is responding.
Links are returned only if they are unchecked or checked earlier than the time when the job started. The job continues until no more unchecked links are received from the database. If a large number of consecutive errors is found for external links, in case of a general network problem with the server running the site, the job stops.
The result of the link validation job is a report called Link Status, in the Episerver CMS Report Center.
Clear generated thumbnail images in the Products list and Media list views and add them again with the Clear Thumbnail Properties job. Run this job manually if you experience problems with refreshing thumbnails.
The Subscription feature lets visitors set the frequency for receiving subscription information. This job checks for information from the system to be included and distributed in the subscription send-out.
Set the frequency of mirroring content between websites with the Mirroring Service job. If your website is set up to mirror content between websites, you can manually mirror content or automatically do so at specific intervals.
Clear the Permanently Mark as Being Edited marking of pages in the edit view (if editors have forgotten to remove the marking).
- Episerver Notification (Enabled and run at an interval of 8 hours)
This feature uses a job scheduler to fetch RSS notifications and to push notifications about Episerver notification (for example, some news at Episerver world)
- Remove Abandoned BLOBs (Enable and runs every week)
Episerver CMS can store media files in a cloud service instead of the website’s database. When you delete CMS files, this job makes sure the stored data is deleted from the BLOB provider.
Deletes the content folders that contain media related to deleted content items.
Lets you define how often the system checks for content versions with a specific future publication date and time.
Set up how often your trash gets emptied with the Automatic Emptying of Trash job. With automatic emptying, all content in trash older than 30 days is permanently deleted by default. You can also manually delete Trash permanently
- Archive Function (Inactive)
Set how often the system archives information after the publication period expires.
Truncates the status of monitored tasks. It is a clean-up job that deletes 30 days of statuses of monitored and completed jobs.
Determine how often Episerver CMS sends notifications of new or updated comments or replies posted in projects by a notification provider (for example, an email provider). Notification messages are sent to:
– users who are tagged in a comment or reply
– users who receive replies to their comments
– users who receive comments on their project actions (such as setting a project item to Ready to publish)
– other users who have previously replied to the same comment
A notification is not sent if no new comments or replies were posted since the job last executed
Truncates or deletes 3 months old notification messages that could not be sent and are still in the system.
Delete items from the change log that are more one month old and do not have any dependencies registered against them by another part of Episerver CMS (for example, Mirroring)
Although was not present on the default empty project create by Episerver CMS Visual Studio Extension version 188.8.131.520, on the documentation CMS – Scheduled jobs is described the Marketing Test Monitor
Handles the starting and stopping of A/B tests based on their start and end dates. If the Automatically publish the winner … setting is enabled, the scheduled job also automatically publishes the winning variant when an A/B test completes, given that the calculated test result is statistically significant with the required confidence level. See A/B Testing configuration in Tool settings.
The job is enabled by default (if you have the A/B Testing feature installed), and set to run every 30 minutes.
This documentation was retrieved from webhelp episerver CMS Schedule job