Scheduled Tasks

Scheduled tasks are events which have been scheduled to run at certain intervals, e.g. once a day, once an hour, or once a week. For instance, you can set up a scheduled task for rebuilding your indexes, for scheduling emails, or for running data integration activities.

The scheduled tasks node gives you access to a list of all scheduled tasks created on the system (Figure 1.1).

Figure 1.1 Scheduled tasks

From the list of scheduled tasks, you can view, run or edit the tasks – or remove them altogether. You can also right-click an existing scheduled task and copy it.

If you need to use custom credentials to run a task you can use the Impersonation button to set them up – this is required if your solution is not hosted by Dynamicweb. Instead, use the credentials for the target windows server environment.

From Dynamicweb 9.3,  you can see when taskexecuter was last executed on this solution above the scheduled task list - the normal interval is every 5 minutes - and will be informed if there is a problem with the serverside scheduled task job.

Scheduled Tasks on SSL servers

You may experience problems with executing scheduled tasks on SSL servers - this is because previous implementations of Scheduled Tasks did not add the -k (--insecure) parameter to tasks on the IIS.

The solution is to delete the task scheduler in Windows Task Scheduler, and force Dynamicweb to create a new instance by creating a new scheduled task.

You can also edit existing tasks and add the -k parameter manually.

"Windows scheduled task is not found"

The Windows scheduled task is not found warning is shown when windows scheduled task is not installed on the server. If you need to suppress this warning - e.g. if the tasks are run on a separate server - this can be done using a setting under Settings > System > Solution settings.

While some scheduled tasks are created automatically by other parts of the system, you can also create scheduled tasks manually by clicking Add in the toolbar to open the scheduled task configuration view (Figure 3.1).

Figure 3.1 Creating a scheduled task

Here you can define the task name, the start time and end time, and the repetition interval, and you can see the Activation URL, which can be used to trigger the scheduled task remotely.

Each task must also have an action (“activation”) associated with it – your options are:

  • Trigger an URL (e.g. a data integration job URL)
  • Call a Method from the API
  • Select an add-in, such as Clean up logs or Run SQL add-in

The following scheduled task add-ins are available out of the box:

Add-in name


PIM Email Notification Add-In

Evaluates & triggers out PIM notification emails.

Build Ecommerce Assortment Items

Rebuilds assortments

Calculate users smart search results

Recalculates user smart searches

Cleanup logs

Evaluates and triggers automatic log cleaning rules

Place recurring order

Places recurring orders

Redeem expired points

Removes expired loyalty points from user accounts

Run SQL add-in

Executes the SQL query defined on the add-in

Feed File Export Task Saved data in a PIM feed to a file
Product version cleanup Automatically purges old versioning data
Build repository index Rebuilds a specific repository index with a particular builder action (partial), and once a day rebuilds a second builder action (full).
Deploy data items from upload folder Deploys depoyment packages located inside a specified folder. Can also send notification emails to report on failures.