question

Hi @Sudheer R, a TS finish task activity doesn’t fit in this logic. DO NOT USE IT!

The classic 3D tasksequence creates a node. This node holds a sequence of tasks. And you dispatch this tasksequence by transferring the node to a dispatcher to let him execute the tasksequence. In fact it is a bit more complicated, because a taskexecuter is always a dispatcher, too.
“task using global list” transfers the node holding the tasksequence to a global list. A taskexecuter looks for an available tasksequence on the global list. If he pulls the node from the list, the dispatcher in the taskexecuter dispatches the taskesequence to execute the tasks by himself.
The TS finish task is renamed in FlexSim 20 and got a different icon. But this is the classic action of dispatching a tasksequence. Because the taskexecuter looks by himself for his jobs, the tasksequence must not dispatched in the process.
The reason is for this approach to replace the 3D dispatcher object by a global list. A dispatcher object can store transferred nodes with tasksequences, but it is much more difficult to identify a special tasksequence and dispatch it to a taskexecuter than if you do it with global lists.
Please think about a planed “to do list”. All jobs are known on the beginning of a shift. But you don’t know who is available when the next job has to be done. If you dispatch the jobs at the beginning of a shift to a distinct numbers of operators, you will probably get a not optimized distribution of jobs over the shift. But if the operators do only one job of the list, and then look for the next job, if they become available, the distribution is a more optimized one.