Cancel Task

You can cancel a task if it is in a queue, and it has not yet started to run. When you cancel a task, it is canceled from the project as a whole, for all users. You can cancel tasks that require no translation so that they do not clutter the task list and require users to handle them.

To cancel a task

From the Task List for a project:

Select the tasks to cancel.
Choose More Options > Cancel Tasks.
Click OK to confirm the cancellation. You have the option of including the canceled task in project cost calculations.

Project cost calculations

The Include in project cost calculation option on the Cancel Tasks dialog tells the system whether a canceled task should be included in the overall project scope report. Depending on when the task is canceled, it may make sense to exclude it from the report.

For example, if the canceled task has not been translated, it probably should be excluded from the project scope report. However, if it already has been translated prior to cancellation, then the translator should be paid and the cost of translating this task included in the project scope report.

The canceled tasks view of the Task List lets you work directly with these tasks. The controls on that view are a subset of the usual Task List buttons, with the following special controls.

View outdated tasks: This checkbox displays those tasks that were canceled and subsequently restarted, so you can evaluate whether to include them in the project scope report.
Include/Exclude Cost: These buttons let you include or exclude canceled tasks from the project cost calculation. Use them at any point after the task has been canceled to adjust the project scope report, if desired.

External tasks

When the running task is an external program, WorldServer can cancel tasks under certain conditions. (A simple example of this is an asset file which has caused an error in one of the Microsoft Office applications.) Use the process_timeout setting in the WorldServer general.properties file to set an upper bound on how long an external running task will persist after a cancel instruction. If process_timeout is set to 1 hour, it wakes up the Workflow Engine and cancels the local WorldServer task after an hour. By default this setting is 0 (zero).