1.6 Managing tasks

Task management functionality lets you check the status and progress of tasks, and control task processing.

The following figure shows the general procedure for automating operating procedures, and how it relates to task management.

Figure 1‒10: Flow of operating procedure automation (task management)

Tasks that have finished processing can be moved from the Tasks list to the History list in a process called archiving. Archiving can be performed manually or automatically. Older task histories moved to the History list can be deleted manually or automatically.

The task management function lets you perform the following tasks:

Tip

For task management you perform in the Tasks window, you can also perform the following operations for debug tasks:

• Managing task progress

• Stopping tasks

• Stopping tasks forcibly

For details about how to perform debug tasks, see the Job Management Partner 1/Automatic Operation Service Template Developer's Guide.

Check the progress of tasks

You can check the status of executed tasks and the processing status. Statuses include the In Progress and Completed statuses, and are updated as tasks are processed.

In the task summary area, you can check the status of the tasks executed by a logged-in user, the status of all tasks in a list, and the progress of a task. You can also check the progress of the flow of the task you selected in the Task Monitor view.

Enter actions for tasks waiting for a response (Enter a response)

You can enter a response when a task requires input from a user.

When a task requires a user to make a decision or selection, it enters Waiting for Response status. You can identify tasks in this status by checking the task summary or tasks list.

When a task enters Waiting for Response status, the appropriate user is notified by email. The email notification feature requires you to specify SMTP server settings, user IDs, and other information. By linking with JP1/IM, you can issue JP1 events reporting that a task has entered Waiting for Response status.

Manage schedules

You can suspend, resume, or cancel waiting or held tasks. You can manage the schedules of only waiting and held tasks. If you want to stop the execution of a task that has already executed, you must perform the processing that stops task execution.

Stop tasks

You can stop a task that is in progress.

When you stop a task, steps that are executing continue processing. Steps that have not started executing yet are not processed. At that time, the task enters the Failed or Completed status. Note that if you stop the task when the window for entering responses is displayed, the user-response operation ends in an error.

Forcibly stop

You can forcibly stop a task that is in progress.

When you forcibly stop a task, the task stops without waiting for steps in progress to be completed. At that time, the task enters the Failed or Completed status. The execution result of a plug-in is not applied to the value of the service property.

If a plug-in that is in progress is a content plug-in, the process tree that is being executed in the target device is forcibly stopped immediately, and the execution result of commands are not guaranteed. For details about operations when the plug-in that is in progress is a basic plug-in, see the related topics section for each basic plug-in in the manual Job Management Partner 1/Automatic Operation Service Template Reference.

Note that if you forcibly stop tasks that are executed regularly, there will be no influence on the next execution.

Resubmit tasks

Tasks that have stopped processing (tasks in the Completed, Failed, or Canceled status) can be executed as a different task with another task ID.

Note that JP1/AO sets Immediate as the execution timing for resubmitted tasks. Change the execution timing as needed.

Retry

You can retry a failed step, or the step after the failed one.

You can retry a task with the same property value and with the same task ID. After retrying a task, you can check the history of the retried tasks in the task log and the public log.

Move (archive) tasks

You can move finished tasks whose results you have checked to the History list.

Tasks moved to the History list can be viewed regardless of category. This allows you to view in a list all tasks that have finished processing.

Tasks are set to be moved regularly to the History list in JP1/AO.

Delete histories

You can delete histories that are no longer require management.

Note that histories are set to be deleted regularly in JP1/AO.

Output (export) task lists

You can output task lists and task histories to a CSV file. You can then use this file to gather and analyze statistics, or use it as a record.

Related topics

• 6.1 Checking the status of tasks executed by the logged-in user

• 6.2 Checking the status of all tasks

• 6.3 Checking the progress of a task

• 6.6 Entering actions for tasks waiting for a response (entering responses)

• 6.7 Suspending tasks (suspending schedules)

• 6.8 Resuming suspended tasks (resuming schedules)

• 6.9 Canceling tasks (canceling schedules)

• 6.10 Stopping tasks (execution stop)

• 6.11 Redoing tasks

• 6.12 Moving tasks to the History list (archiving tasks)

• 6.13 Deleting task histories

• 6.14 Outputting task lists (exporting tasks)

Organization of this section

• 1.6.1 Overview of task management

• 1.6.2 Managing schedules

• 1.6.3 Managing task progress

• 1.6.4 Behavior when tasks are stopped

• 1.6.5 Behavior when tasks waiting for a response have stopped

• 1.6.6 Behavior when a task has stopped while repeated execution plug-ins are running

• 1.6.7 Behavior when a task is forcibly stopped

• 1.6.8 Retrying tasks

• 1.6.9 Archiving tasks and removing histories automatically

• 1.6.10 Display format of task summary

• 1.6.11 Task categories and generation timing

• 1.6.12 Task statuses and status transitions

• 1.6.13 Step statuses

• 1.6.14 Maximum number of plug-ins contained in a task that can be executed concurrently

• 1.6.15 Retention periods for task histories

To Page Top