Task Sequence Sub Flow behavior with Source

[clairekruppGhafari]

[ FlexSim 18.2.2 ]

I am working through the Tutorial on using a Task Sequence Sub Flow to create separate instances for each operator when unloading the processors. Only one token is created by each processor for each unload task as predicted. So then I decided to add my own spin and use the same logic to use one of the operators to carry the Item from the Source to the first processor. I copied the logic EXACTLY. But when the Source calls for an operator it creates TWO tokens, one for each instance. Both of them go through the logic at the same time, but the second operator does not actually do anything (which is correct).

So why is the second token created? And how is it able to go through the second instance of the sub flow without actually waiting for the second operator to perform the Load and Unload activities?

(I have already read all the related sections in the User Manual regarding Sub Flows, Instances and Task Sequence Sub Flows. None of them mention anything about Sources acting differently from other fixed resources.)

[SCHamoen]

@Claire K It would help us enormously if you would attach your model...

[clairekruppGhafari]

Sure, here it is....

process-flow-tut-21-task-sequences-claire-k.fsm

[joshua_s · Accepted solution]

This is occurring because every time you restart the model, nothing is attached to the subflow processflow activity. The operators are only attached after they receive their first task. So when you want to see the individual process flows for the instances of the original TransportItems subflow, you can pull it up without problem while the model is running, but as soon as you restart the model, they lose their references, and so will default to showing the original subflow.

[clairekruppGhafari]

Thanks for the insight @Joshua S, I did confirm that it happens with the processors too, so it is a problem with display not with execution. That is going to be a pain when I am debugging!