Previous topic Next topic JavaScript is required for the print function Mail us feedback on this topic! Mail us feedback on this topic!  

The Scheduler allows you to define when specified scheduled tasks will be executed. This is useful when you want some tasks to be executed automatically at a specific time or over a time period. You can configure the scheduled tasks in Site Manager -> Administration -> Scheduled tasks.


The Site drop-down list is used for selecting a site. After selecting a site, a list of tasks scheduled for the site will be displayed in the table below. Tasks that aren't limited to a single site can only be seen when (Global) is selected.


The process of creating a new scheduled task is covered in more detail in the Developer's Guide -> Development -> Scheduler -> Scheduling a custom code topic.


The Scheduler interval setting, which can be found at CMS Site Manager -> Settings -> System, determines how often tasks are automatically checked if they are ready to be executed.


Additional low-level scheduler settings can be done by adding the keys listed in the Scheduler settings section of Appendix C - Web.config parameters of the Developer's Guide into the /configuration/appSettings section of your web.config file.


The Developer's Guide -> Development -> Scheduler -> Scheduler internals and API sub-chapter provides information about the database tables and classes used by the module and examples of how scheduled tasks can be managed using the API.


In addition to other functions, the scheduler is used to execute tasks for the following modules:


Content staging
E-commerce (E-commerce Guide -> Configuration settings -> Deleting old shopping carts)
E-mail queue
On-line users
Smart search
Time zones
Web analytics
Web farm synchronization




Scheduling reliability


Since the scheduling process runs within the ASP.NET process, it may not be executed if your website is not running. This happens when the process is recycled without being started again (after a long period of website inactivity). It means that your scheduled tasks will not be executed in such cases.


If you want to run the scheduling reliably, it's necessary to ensure that your website is always running. You can do that by using some utility or an external service that requests the home page of your website on a regular basis.


Page url: http://devnet.kentico.com/docs/5_5r2/contexthelp/index.html?scheduled_tasks_overview.htm