Scheduled Tasks

The default view lists all your scheduled tasks in alphabetical order. For each task, you will see a scheduled task Type, whether the task is Enabled, as well as the timing of its Last run and/or Next run.

You can create your own personalized view of the table by filtering the condition sets or adding/deleting columns and clicking Save as in the Views drop-down.

Selecting multiple table rows

Adjacent rows: Click on the first row, then hold down the Shift key and click on the last row in the range
Non-adjacent rows: Hold down the Ctrl key (or "Command" on Mac) and click on each row you want to select
Adjacent rows, using only the mouse: Click and hold the left mouse button on the first row, then drag the cursor up or down across the rows to highlight the desired ones

Create a scheduled task

To create a scheduled task:

1. On the Scheduled Tasks page, click the Create button in the table's toolbar.

2. In the Create scheduled task window that opens, choose a task Type. Click Next.

3. Give the task a name and add a description, if desired.

4. Choose whether the task is Enabled. Click Next.

5. Set how often the task should run (in days). Click Next.

6. On the Summary tab, choose whether the task can be modified after it is created. Click Finish.

To edit the details for a scheduled task, select the scheduled task and click the Edit button.

Manually initiate a scheduled task

To manually trigger a scheduled task, click Start.

View scheduled task details

Double-click on a scheduled task to view and manage its details.

Overview tab

A few basic options to configure the scheduled task.

Server - This scheduled task is only run on the specified server. If no server is specified, any server can execute the scheduled task.
Allow task to be run on demand - If selected, the scheduled task can be started only manually by an administrator, otherwise it can only be started by a schedule.
If task is already running - Set what the system should do if a task is already running:

Do not start a new instance - A new task won't be started when this task is still running.
Run a new instance in parallel - Always start a new task, even if this task is still running.
Queue a new instance - Queue a new task and run it immediately after the currently running task is finished.

Notifications tab

Displays the email addresses of those who receive a notification after a scheduled task runs.

For system tasks provided by Application Workspace, the notification option will use the mail servers that are defined in the primary zone, if available.

Only send errors and task updates

When enabled, a mail notification will be sent only if there is something notable to report, like:
- The task has failed to run.
- The task has information to report.
When disabled, a mail notification will always be sent after the task ran, regardless of the results.

Schedule tab

Create schedules for this task. There are four types of schedules: daily, weekly, monthly and interval.

History tab

Shows a list of all the times the task ran.

State - Whether or not the scheduled task was successful or if it is still in progress.
Started by - Which identity was responsible for triggering the scheduled task.
Device - Which server executed the scheduled task.

Auditing tab

A comprehensive log of changes to this scheduled task, displaying the identity behind each modification.
NOTE: This tab is only available if auditing is enabled in the Database Event Collector. For more information, see Auditing.

Clean auditing

This task removes auditing events that are older than a specific number of days.
Clean auditing scheduled tasks can be defined at either the system or zone level:

System tasks apply across all zones.
Zone tasks apply only within their specific zone.

The system-level task has a default clean-up audit period of 30 days.
If a zone-level task is set to 15 days, both the system-level and zone-level task will run independently.
However, if a zone-level task is set to run after 45 days, the system-level task will still clean up data after 30 days, overriding the longer zone-level period.

Disabling this scheduled task will cause the auditing events table to grow uncontrollably. We therefore do not recommend disabling this task.