In the attached models if I use a Operator the model Works fine, but using a TaskExecuter the model crashes.operator.fsmtaskexecuter.fsm
You've actually put FlexSim into an infinite loop. Normally Process Flow is able to detect infinite loops and allow you to stop your model during one. But in this case it looks like that isn't possible.
The TaskExecuter doesn't have a navigator when you first create it. I've discussed this with some of the other developers and we're not really sure why this is the case. It seems that it may have been important many versions ago. We should have it connect to the default navigator when it's created.
The issue is that, without the navigator, the TE only performs offset travel. So when you tell the TE to travel to a Queue using a regular Travel Activity, it says, I'm already there, and moves on to the next activity. In your model's case, this causes the token to move through the same 4 activities indefinitely with no breaks.
To fix this model, drag an operator into your model (to create the default navigator) and then open the TE's properties window and set the Navigator to DefaultNavigator. We'll fix this for future releases of FlexSim.
10 People are following this question.
