1.6.5 Automatically archiving tasks and deleting task histories

JP1/AO is configured to automatically archive and delete tasks and task histories.

Automatically archiving tasks

Once a day, JP1/AO archives processed tasks that satisfy the following criteria, in the following order:

Tasks whose retention period has elapsed
Tasks exceeding the maximum number of tasks that can be retained

Tasks exceeding the maximum number of tasks that can be retained are archived starting from the task with the oldest end time.

Note that the maximum number of tasks that can be retained includes debug tasks.

You can change the retention period and maximum number of retained tasks by editing the user-specified properties file (config_user.properties).

Tip: JP1/AO deletes debug tasks as part of the process of automatically archiving tasks. For details on the automatic deletion of debug tasks, see the topic that describes the procedure for checking the progress of debug tasks from the Tasks window in the JP1/Automatic Operation Service Template Developer's Guide.

Automatically deleting task histories

JP1/AO can automatically delete task histories that satisfy certain criteria.

Histories exceeding the maximum number of histories that can be retained are deleted once a day. Deletion starts from the task that was archived earliest.

You can change the maximum number of retained task histories by editing the user-specified properties file (config_user.properties).