Menu:


AngeliaScheduler - Remote Queue Manager - Main Form - click to see it full size AngeliaScheduler - Remote Queue Manager - Core Configuration - click to see it full size AngeliaScheduler - Remote Queue Manager - Queue Configuration - click to see it full size


AngeliaSchedulerTM - On-Line Help - Purging Completed Tasks




In order to avoid clogging the configuration database with completed tasks, AngeliaScheduler provides a means to purge completed tasks from the configuration from time to time.  Completed Task Purging is optional – and is controlled by the settings of various Core Service configuration items.  Purging may be configured to be either Manual, in which case a Remote User with Purge Access Rights must select the "Purge Completed Tasks" menu item under the "Modify" button in the Remote Queue Manager too bar, or it may be set up to be automatic.

If Automatic Purging is selected then there are two options available to control when tasks are purged.  You may choose to purge completed tasks daily at a certain time, or you may choose to have purging done each time a task completes.  In either case, the number of tasks to remain on the queue of each type ("Completed", "Cancelled", "Failed", and "Aborted") can be defined – either my defining a maximum number of tasks of each type to remain on the queue, or by specifying a maximum age (in days) beyond which tasks will be purged.

A Note On Completed Task Status:  A task is said to be "Completed" whenever it has been executed by the AngeliaScheduler Service and the process that was created has terminated of its own volition.  AngeliaScheduler has no way of knowing if, for example, you used the Task Manager to prematurely terminate the process – nor does it have any intrinsic way of knowing whether or not your application performed correctly and completely.  To provide a means to communicate a "run but failed" task condition back to AngeliaScheduler, each task is created with an environment variable named "TaskFailedPath" that contains a full path name specific to that task.  Creating a file at "TaskFailedPath" will signal AngeliaScheduler that your task did not complete normally, and it will indicate as "Failed" in AngeliaScheduler Task displays.  AngeliaScheduler will erase the file at TaskFailedPath at task termination if it exists.  An AngeliaScheduler Task is said to be "Aborted" if the task was terminated prematurely from AngeliaScheduler by setting the task’s status to "Aborted".  A "Cancelled" task is one that was cancelled prior to execution.

Further discussion and documentation of specific Task Purging Options is available in the Completed Task Purging section under the Desktop Configuration Utility.