Scheduled Tasks

Aurea List Manager performs certain tasks such as sending out digests or cleaning the database of old posts automatically at preset times.

By default, database intensive tasks (such as deleting old data) are scheduled for various times in the middle of the night. Other tasks, such as notifying you that your database is reaching capacity, are scheduled during the day.

These tasks may be rescheduled here to occur at different intervals or at different times of the day, or to not occur at all. For example, by changing the time and frequency of scheduled tasks, you may schedule digests to be sent more than once a day, or at a different time of day.

There is no default time and frequency for the "Apply member ban rules" task. This task sets members who match ban rules to be unsubscribed.

You may not add or delete scheduled tasks. If you do not want a scheduled task to occur, erase the time when the task is supposed to be performed.

Installations using Microsoft SQL or MSDE for its database has a "DB Maintenance" scheduled task available. This task is disabled by default, but should be enabled by users who have not otherwise implemented database maintenance to reindex and defragment the database. Note: Lyris Technologies does not provide technical support for installation, use or maintenance of MS SQL or Oracle.

Click restore defaults to restore the default scheduled task times and frequency to all scheduled tasks. Click edit next to a task to edit it.

Task

The name of the task. The name may not be edited.

Description

A description of the task. The description may not be edited.

Next Run Time

If enabled, the next time the scheduled task is scheduled to run. Specifying a different run time causes the scheduled task to run at that time of day at the frequency you specify in Frequency. Enter the next run time in yyyy-mm-dd hh:mm:ss format. Example:

2004-06-30 13:01:01

If you do not want this task to run, select Disable.

Previous Start Time

The time this task last started, if it has run in the past. If the task was scheduled to run and did not, it is possible that it is interfering with another task (e.g., server down time).

Previous End Time

The time this task last ended, if it has run in the past. A long period of time between the task start and end times may indicate task conflicts.

Frequency

How frequently the task is run. By default, most scheduled tasks occur once a day. You may select a different frequency here. The frequency selected here causes the run time to be updated appropriately.

For example, if you set the run time to be 13:01:01, and select the frequency to be every 12 hours, the run time will be automatically updated so that the task will be performed at 13:01:01 and at 01:01:01 each day.