question

Please read the Manual Reference Tasksequence. The operator belongs to the object class Taskexecuter. If you want that a taskexecuter do something you give him a sequence of task to do. You can start with the source code example in the field Use Transport on the Flow tab of a property window of a fixed resource (queue, processor) . The template is called Tasksequence example 1. It is the classic transport task sequence:

• travel to Loadstation
• load item at Loadstation
• break and look for other transport task sequences, if there is transport capacity left
• travel to unloadstation
• unload item in unloadstation

If you know the delay, when you create a tasksequence, you use the TASKTYPE_DELAY. Otherwise you use the TASKTYPE_BREAK or TASKTYPE_CALLSUBTASK to call an OnMessage trigger to insert a delay in the current executed tasksequence dynamically.

If you don't know, when the delay is going to end, then you can replicate the tasksequence, which let a taskexecuter assist by a setup or processing. The tasksequence contains a TASKTYPE_UTILIZE which place the taskexecuter in a state and let him wait. When the time comes, the operator should do something useful again, you call the freeoperators - command on the taskexecuter or its controlling dispatcher.

If you want that a currently active tasksequence is interrupted, you set the preempt option to PREEMPT_ONLY in the source code line where you create the tasksequence. At the time when you dispatch the tasksequence the active tasksequence is going to break and will continue when the preempting tasksequence is finished.

But in ProcessFlow this would be much easier, because you would only insert a delay activity in the flow the token takes to control the tasks the operator does.