Tasks Not Triggering When Duplicate Task is Used

 

Summary

An issue has been identified affecting Automate versions 6.0.0, 6.0.1, 6.0.2 and 6.0.3 when using the "Dupilicate Task" feature.

Symptoms

Tasks do not trigger (scheduled or/and other trigger) after the "Duplicate task" feature. Usually the original task will stop running when it is supposed to and only the last task created via the "duplicate task" feature will continue running when the trigger condition occurs.

Workaround

For all tasks created via the "duplicate task" feature, go to the task properties Trigger tab, delete the trigger then re-create it via the Add button. Simply editing the trigger will not fix the problem. After you have recreated the triggers you must restart all Automate applications for the new trigger id's to take effect.

Reason

This is a bug in the "duplicate task" feature in the Task Administrator. Triggers on duplicated tasks retain their original Trigger ID which should be unique. Therefore, after duplicating a task only one task will trigger, usually the last created one because it appears last in the task list.

This issue will be fixed in the 6.0.4 update due out in August 2005. Until then either avoid the duplicate task feature or if you use it, be sure to recreate the trigger and restart all Automate applications.

We apologize for any inconvenience this may have caused you.

Applies To: Automate 5, Automate 6