8.4.5 Procedure for forcibly stopping debug tasks
The following describes how to forcibly stop a debug task that is still in progress. You can forcibly stop debug tasks that are in the status of In Progress, Waiting for Input, In Progress (with Error), or In Progress (Terminating).
If you want to stop a running debug task and perform the debug process again, you can forcibly stop the debug task from the Service Builder Debug window.
If you inadvertently close the Web browser window from which you are using JP1/AO while a debug task is in progress, use the Tasks window to forcibly stop the debug task. You can also use this window to forcibly stop a debug task executed by another user.
Debug tasks that are forcibly stopped enter Failed status.
If the debug task contains an interrupted step, the debug task stops after the step is automatically resumed, without executing the plug-in processing.
- Tip
For details about the difference between stopping and forcibly stopping tasks, see Managing Tasks in the JP1/Automatic Operation Administration Guide.
To forcibly stop a debug task from the Service Builder Debug window:
In the Debug area of the Service Builder Debug window, click the Forcibly Stop button (
![[Figure]](GRAPHICS/F0000010.GIF)
).In the Information dialog box, click OK.
Operation results
The debug task enters Failed status.
To forcibly stop debug tasks from the Tasks window:
In the Tasks window, click the Debug tab.
In the list of tasks, select the debug tasks that you want to forcibly stop.
- Tip
You can select multiple debug tasks by selecting check boxes beside the task names.
In the More Actions pull-down menu, click Forcibly Stop.
In the Forcibly Stop dialog box, confirm the debug tasks to be stopped forcibly, and then click OK.
In the Information dialog box, click OK.
Operation results
The selected debug tasks enter Failed status.